This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: gdb remote serial packet has wrong address
- From: Michael Snyder <msnyder at vmware dot com>
- To: "raja dot saleru at iap-online dot com" <raja dot saleru at iap-online dot com>
- Cc: "gdb at sourceware dot org" <gdb at sourceware dot org>
- Date: Wed, 26 Nov 2008 10:45:01 -0800
- Subject: Re: gdb remote serial packet has wrong address
- References: <33036.210.143.35.19.1225860010.squirrel@www.iap-online.com> <59596.210.143.35.18.1226650013.squirrel@www.iap-online.com> <28893.210.143.35.18.1227662836.squirrel@www.iap-online.com>
raja.saleru@iap-online.com wrote:
> Hi,
>
> I am trying to debug the application running on arm based target,
> gdb,OpenOCD.
>
> I am using watch points to debug the application.
>
> In debug mode, the below RSP communication shows that the address for the
> packets m, Z2 and Z0 shows wrong. Is it so ?
> If yes, what can be the wrong ? Any hint to debug either at gdb side or
> OpenOCD side ?
>
> Is there any possibility of addresses can become single degit like this ?
Could be truncation? From 64 bit to 32 bit, eg.?
What target architecture does gdb report?
> Breakpoint 1, main () at test.c:13
> 13 int x = 10, y = 2;
> (gdb) watch x
> Sending packet: $p8#a8...Ack
> Packet received: fdffffff
> Sending packet: $m1,4#fe...Ack
> Packet received: 00000000
> Sending packet: $m560,48#a0...Ack
> Packet received:
> 80264402603e0680185c0a00603e0200185c0200603e0400683e0400005e010
> 0603e0200093c0000493cdc2e185c0b00083a683e0220683e04000844881c0400001fa002001eda0
> 2
> Sending packet: $m9,4#06...Ack
> Packet received: 05000000
> Sending packet: $m9,4#06...Ack
> Packet received: 05000000
> Hardware watchpoint 2: x
> (gdb) c
> Continuing.
> Sending packet: $Hc0#db...Ack
> Packet received:
> Sending packet: $s#73...Ack
> Packet received: T05
> Sending packet: $p1e#06...Ack
> Packet received: 6c050000
> Sending packet: $Z0,568,2#b7...Ack
> Packet received: OK
> Sending packet: $p8#a8...Ack
> Packet received: fdffffff
> Sending packet: $m560,48#a0...Ack
> Packet received:
> 80264402603e0680185c0a00603e0200185c0200603e0400683e0400005e010
> 0603e0200093c0000493cdc2e185c0b00083a683e0220683e04000844881c0400001fa002001eda0
> 2
> Sending packet: $m1,4#fe...Ack
> Packet received: 00000000
> Sending packet: $Z2,1,4#49...Ack
> Packet received: E10
> Packet Z2 (write-watchpoint) is supported
> Sending packet: $Z2,0,4#48...Ack
> Packet received: E10
> Sending packet: $z2,1,4#69...Ack
> Packet received: OK
> Sending packet: $z2,0,4#68...Ack
> Packet received: OK
> Sending packet: $Z0,5,2#49...Ack
> Packet received: OK
> Warning:
> Could not insert hardware watchpoint 2.
> Could not insert hardware breakpoints:
> You may have requested too many hardware breakpoints/watchpoints.
>
> (gdb)
>
> Thanks in Advance
> Raja Saleru
>