From: Corinna Vinschen <vinschen@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFA] i386-tdep.c: Remove call to inside_entry_file
Date: Thu, 10 Apr 2003 13:19:00 -0000 [thread overview]
Message-ID: <20030410131924.GA16613@cygbert.vinschen.de> (raw)
In-Reply-To: <86u1db8tu8.fsf@elgar.kettenis.dyndns.org>
On Sun, Apr 06, 2003 at 06:38:07PM +0200, Mark Kettenis wrote:
> Therefore, I think it's best to apply your alternative patch. Your
> second version is herewith approved.
Thanks. I've applied a changed version which additionally defines
a new frame_chain_valid function for Cygwin. This exactly eliminates
all FAILs in gdb.asm/asm-source.exp.
Corinna
2003-04-10 Corinna Vinschen <vinschen@redhat.com>
* i386-cygwin-tdep.c (i386_cygwin_frame_chain): New function.
(i386_cygwin_init_abi): Set i386_cygwin_frame_chain as new
frame_chain function.
* Makefile.in: Add dependencies due to above change.
Index: Makefile.in
===================================================================
RCS file: /cvs/src/src/gdb/Makefile.in,v
retrieving revision 1.360
retrieving revision 1.361
diff -p -u -r1.360 -r1.361
--- Makefile.in 6 Apr 2003 01:13:58 -0000 1.360
+++ Makefile.in 10 Apr 2003 13:15:50 -0000 1.361
@@ -1798,7 +1798,7 @@ i386gnu-tdep.o: i386gnu-tdep.c $(defs_h)
i386ly-tdep.o: i386ly-tdep.c $(defs_h) $(gdbcore_h) $(inferior_h) \
$(regcache_h) $(target_h) $(i386_tdep_h) $(osabi_h)
i386-cygwin-tdep.o: i386-cygwin-tdep.c $(defs_h) $(gdb_string_h) \
- $(i386_tdep_h) $(osabi_h)
+ $(i386_tdep_h) $(osabi_h) $(gdbcore_h) $(frame_h) $(dummy_frame_h)
i386nbsd-tdep.o: i386nbsd-tdep.c $(defs_h) $(gdbtypes_h) $(gdbcore_h) \
$(regcache_h) $(arch_utils_h) $(i386_tdep_h) $(i387_tdep_h) \
$(nbsd_tdep_h) $(solib_svr4_h) $(osabi_h)
Index: i386-cygwin-tdep.c
===================================================================
RCS file: /cvs/src/src/gdb/i386-cygwin-tdep.c,v
retrieving revision 1.1
retrieving revision 1.2
diff -p -u -r1.1 -r1.2
--- i386-cygwin-tdep.c 21 Mar 2003 10:07:17 -0000 1.1
+++ i386-cygwin-tdep.c 10 Apr 2003 13:15:50 -0000 1.2
@@ -20,8 +20,37 @@ Foundation, Inc., 59 Temple Place - Suit
#include "defs.h"
#include "gdb_string.h"
+#include "gdbcore.h"
#include "i386-tdep.h"
#include "osabi.h"
+#include "frame.h"
+#include "dummy-frame.h"
+
+static int
+i386_cygwin_frame_chain_valid (CORE_ADDR chain, struct frame_info *thisframe)
+{
+ /* In the context where this is used, we get the saved PC before we've
+ successfully unwound far enough to be sure what we've got (it may
+ be a signal handler caller). If we're dealing with a signal
+ handler caller, this will return valid, which is fine. If not,
+ it'll make the correct test. */
+ return ((get_frame_type (thisframe) == SIGTRAMP_FRAME) || chain != 0);
+}
+/* Return the chain-pointer for FRAME. In the case of the i386, the
+ frame's nominal address is the address of a 4-byte word containing
+ the calling frame's address. */
+static CORE_ADDR
+i386_cygwin_frame_chain (struct frame_info *frame)
+{
+ if (pc_in_dummy_frame (get_frame_pc (frame)))
+ return get_frame_base (frame);
+
+ if (get_frame_type (frame) == SIGTRAMP_FRAME
+ || i386_frameless_signal_p (frame))
+ return get_frame_base (frame);
+
+ return read_memory_unsigned_integer (get_frame_base (frame), 4);
+}
static void
i386_cygwin_init_abi (struct gdbarch_info info, struct gdbarch *gdbarch)
@@ -29,6 +58,8 @@ i386_cygwin_init_abi (struct gdbarch_inf
struct gdbarch_tdep *tdep = gdbarch_tdep (gdbarch);
tdep->struct_return = reg_struct_return;
+ set_gdbarch_deprecated_frame_chain (gdbarch, i386_cygwin_frame_chain);
+ set_gdbarch_deprecated_frame_chain_valid (gdbarch, i386_cygwin_frame_chain_valid);
}
static enum gdb_osabi
--
Corinna Vinschen
Cygwin Developer
Red Hat, Inc.
mailto:vinschen@redhat.com
prev parent reply other threads:[~2003-04-10 13:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-01 15:44 Corinna Vinschen
2003-04-01 15:57 ` Andrew Cagney
2003-04-01 16:21 ` Corinna Vinschen
2003-04-06 16:38 ` Mark Kettenis
2003-04-10 13:19 ` Corinna Vinschen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030410131924.GA16613@cygbert.vinschen.de \
--to=vinschen@redhat.com \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox