From: "Decker, Paul" <Paul.Decker@analog.com>
To: "Daniel Jacobowitz" <drow@false.org>,
"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:47:00 -0000 [thread overview]
Message-ID: <E21A9A52FF03B249B20F0DC563DEBB31191D46C9@nwd2exm3.ad.analog.com> (raw)
The "set debug remote 1" and "set debug frame 1" options seem to be good
things to know.
(gdb) set debug remote 1
(gdb) set debug frame 1
(gdb) target remote :1234
Remote debugging using :1234
Sending packet: $Hc-1#09...Ack
Packet received: OK
Sending packet: $qC#b4...Ack
Packet received:
Sending packet: $qOffsets#4b...Ack
Packet received:
Sending packet: $?#3f...Ack
Packet received: T00
{ flush_cached_frames () }
Sending packet: $Hg0#df...Ack
Packet received: OK
Sending packet: $p0#a0...Ack
Packet received:
Sending packet: $g#67...Ack
Packet received:
0600a0ff000008601400000104c8cbcfde367ffc01000000000000000dc8dd8
855017bb00000140004c8de36010000000dc8550108600001cbcf7ffc00000000dd887bb
0001404d
e01000d550810e0ff10e3fc8819f35d4ad837fc0a0400000022d02e983ab058a83ca8f09
00000000
00000000000000000000000000000000008b1eecfb4d23c56b1b6f89af80fb0ff9836bd4
8dcb1bc4
800000000000000000000000000000000000000000000002000000000010000000000800
34300010
000000000000044440bc001000000180100ef5a0000effeff7eff0600a0ff4463827e000
03044082
0000000ef08ef000030442000000000002000304400000013e0ff0404e0ff0003e0ff010
00000000
000000000a0ff0000000000000000
{ 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>,p
c=<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 *a
ddrp=0x0 *bufferp=[0600a0ff] }
{ get_frame_id (fi=0) { frame_register_unwind
(frame=-1,regnum=51(FP),...) -> *o
ptimizedp=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 *a
ddrp=0x0 *bufferp=[0600a0ff] }
{ frame_id_p (l={!stack,!code,!special}) -> 0 }
Value being assigned to is no longer active.
(gdb) p/x $FP
{ frame_register_unwind (frame=-1,regnum=51(FP),...) -> *optimizedp=0
*lvalp=2 *
addrp=0x94 *bufferp=[dcb1bc48] }
$2 = 0x48bcb1dc
(gdb) set $FP=0x0
{ frame_register_unwind (frame=-1,regnum=51(FP),...) -> *optimizedp=0
*lvalp=2 *
addrp=0x94 *bufferp=[dcb1bc48] }
{ frame_id_p (l={!stack,!code,!special}) -> 0 }
Value being assigned to is no longer active.
(gdb) p/x $SP
{ frame_register_unwind (frame=-1,regnum=49(SP),...) -> *optimizedp=0
*lvalp=2 *
addrp=0x8c *bufferp=[f80fb0ff] }
$3 = 0xffb00ff8
(gdb) set $SP=0
{ frame_register_unwind (frame=-1,regnum=49(SP),...) -> *optimizedp=0
*lvalp=2 *
addrp=0x8c *bufferp=[f80fb0ff] }
{ frame_id_p (l={!stack,!code,!special}) -> 0 }
Value being assigned to is no longer active.
(gdb)
-----Original Message-----
From: gdb-owner@sources.redhat.com [mailto:gdb-owner@sources.redhat.com]
On Behalf Of Daniel Jacobowitz
Sent: Tuesday, May 03, 2005 9:41 AM
To: Decker, Paul
Cc: gdb@sources.redhat.com
Subject: Re: Value being assigned to is no longer active.
On Tue, May 03, 2005 at 09:38:18AM -0400, Decker, Paul wrote:
> Also, I've made my debug server print out the packets it sends and
> receives, this is what is sent from the target to gdb.
You can get some similar information from gdb with "set debug remote".
Could you redo this with both "set debug remote 1" and "set debug frame
1" before you issue the "target remote" command?
--
Daniel Jacobowitz
CodeSourcery, LLC
next reply other threads:[~2005-05-03 13:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-03 13:47 Decker, Paul [this message]
2005-05-03 13:54 ` Daniel Jacobowitz
-- 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=E21A9A52FF03B249B20F0DC563DEBB31191D46C9@nwd2exm3.ad.analog.com \
--to=paul.decker@analog.com \
--cc=drow@false.org \
--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