From: Daniel Jacobowitz <drow@false.org>
To: "Decker, Paul" <Paul.Decker@analog.com>
Cc: gdb@sources.redhat.com
Subject: Re: Value being assigned to is no longer active.
Date: Tue, 03 May 2005 13:54:00 -0000 [thread overview]
Message-ID: <20050503135408.GA22997@nevyn.them.org> (raw)
In-Reply-To: <E21A9A52FF03B249B20F0DC563DEBB31191D46C9@nwd2exm3.ad.analog.com>
On Tue, May 03, 2005 at 09:46:40AM -0400, Decker, Paul wrote:
>
>
> The "set debug remote 1" and "set debug frame 1" options seem to be good
> things to know.
Yep. Please fix your line wrapping; I've manually unwrapped this so
that I can read it.
> { create_sentinel_frame (...) -> {level=-1,type=<unknown> type>,unwind=0x8227310,pc=<unknown>,id={!stack,!code,!special},func=<unknown>} }
> { get_prev_frame_1 (this_frame=-1) -> {level=0,type=<unknown>,unwind=<unknown>,pc=<unknown>,id=<unknown>,func=<unknown>} }
> { deprecated_update_frame_pc_hack (frame=0,pc=0xffa00006) }
> { frame_register_unwind (frame=-1,regnum=49(SP),...) -> *optimizedp=0 *lvalp=2 *addrp=0x8c *bufferp=[f80fb0ff] }
> Sending packet: $mffa00002,c#1b...Ack
> Packet received: 000000000000000000000000
> 0xffa00006 in ?? ()
> (gdb) p/x $PC
> { frame_register_unwind (frame=-1,regnum=0(PC),...) -> *optimizedp=0 *lvalp=2 *addrp=0x0 *bufferp=[0600a0ff] }
> { get_frame_id (fi=0) { frame_register_unwind (frame=-1,regnum=51(FP),...) -> *optimizedp=0 *lvalp=2 *addrp=0x94 *bufferp=[dcb1bc48] }
> { frame_func_unwind (fi=-1) -> 0x0 }
> -> {!stack,!code,!special} }
> $1 = 0xffa00006
> (gdb) set $PC=0xFFA00000
> { frame_register_unwind (frame=-1,regnum=0(PC),...) -> *optimizedp=0 *lvalp=2 *addrp=0x0 *bufferp=[0600a0ff] }
> { frame_id_p (l={!stack,!code,!special}) -> 0 }
> Value being assigned to is no longer active.
The key here is that nothing claims the code at 0xffa00006 as any kind
of frame. That means we end up with no frames at all except for the
special sentinal frame (at -1).
One solution would be to make sure that some frame sniffer for your
target does accept this frame. Another would be to handle this in
common code by creating a special frame sniffer, at the end of the
list, which always accepts frame ID 0. I'm not sure how practical that
is (haven't thought about it much).
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-05-03 13:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-03 13:47 Decker, Paul
2005-05-03 13:54 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-03 14:01 Decker, Paul
2005-05-03 13:38 Decker, Paul
2005-05-03 13:40 ` Daniel Jacobowitz
2005-05-03 13:03 Decker, Paul
2005-05-03 13:21 ` Daniel Jacobowitz
2005-05-03 12:41 Decker, Paul
2005-05-03 12:58 ` Daniel Jacobowitz
2005-04-20 23:58 Shaun Jackman
2005-04-21 0:47 ` Daniel Jacobowitz
2005-04-21 3:16 ` Shaun Jackman
2005-04-21 3:18 ` Daniel Jacobowitz
2005-04-21 3:41 ` Shaun Jackman
2005-04-27 16:39 ` Shaun Jackman
2005-04-27 18:40 ` Daniel Jacobowitz
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=20050503135408.GA22997@nevyn.them.org \
--to=drow@false.org \
--cc=Paul.Decker@analog.com \
--cc=gdb@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