From: Andrew Cagney <ac131313@redhat.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] mips-tdep.c: Fix inferior function call breakage
Date: Mon, 27 Jan 2003 22:59:00 -0000 [thread overview]
Message-ID: <3E35B9B2.5060104@redhat.com> (raw)
In-Reply-To: <1030127195746.ZM23807@localhost.localdomain>
Hmm, this a different, but related, stack dump. The old backtrace was
for before the inferior function call had even been started. The below
is for when the target has stopped in the dummy frame code after the
inferior function returns.
Read the next bit bottom up:
> #3 0x080c670c in gdbarch_init_extra_frame_info (gdbarch=0x82d91e0,
> fromleaf=0, frame=0x82ceed8)
> at /ocotillo2/sourceware-mips64/ocotillo-cross-mips64/../src/gdb/gdbarch.c:4422
> #4 0x08106e57 in create_new_frame (addr=1099511626816, pc=268437552)
> at /ocotillo2/sourceware-mips64/ocotillo-cross-mips64/../src/gdb/frame.c:890
2. GDB starts to go wrong with the above call.
However, I've just committed the sentinel-frame patch and
create_new_frame() is no longer called. Instead get_prev_frame() will
call init_extra_frame_info directly (the call goes with a nasty comment
:-)) and, hence, the problem will still occure.
> #5 0x081066b5 in get_current_frame ()
> at /ocotillo2/sourceware-mips64/ocotillo-cross-mips64/../src/gdb/frame.c:506
1. Ok so far.
> #6 0x08089261 in bpstat_stop_status (pc=0x82b2f20, not_a_sw_breakpoint=0)
> at /ocotillo2/sourceware-mips64/ocotillo-cross-mips64/../src/gdb/breakpoint.c:2724
> #7 0x080b621f in handle_inferior_event (ecs=0xbfffee00)
> at /ocotillo2/sourceware-mips64/ocotillo-cross-mips64/../src/gdb/infrun.c:1805
I can see two options:
- Modify get_prev_frame() to not call init extra info when in a dummy
frame. Not to sure about this.
- Modify mips_init_extra_frame_info() to return immediatly when a dummy
frame.
Note that there is ment to be only one call to pc_in_dummy_frame() (in
"frame.c") and even that is going away - I'm going to deprecate that
function.
Andrew
next prev parent reply other threads:[~2003-01-27 22:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-23 7:26 Kevin Buettner
2003-01-23 17:00 ` Daniel Jacobowitz
2003-01-23 21:00 ` Andrew Cagney
2003-01-23 22:42 ` Daniel Jacobowitz
2003-01-24 3:55 ` Kevin Buettner
2003-01-27 19:21 ` Andrew Cagney
2003-01-27 19:57 ` Kevin Buettner
2003-01-27 22:59 ` Andrew Cagney [this message]
2003-01-27 23:57 ` Kevin Buettner
2003-01-28 13:14 ` Andrew Cagney
2003-01-28 16:32 ` Kevin Buettner
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=3E35B9B2.5060104@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=kevinb@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