This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
remote/1835: An error packet in reply to an 'm' packet is not treated as an error
- From: trini at kernel dot crashing dot org
- To: gdb-gnats at sources dot redhat dot com
- Date: 21 Dec 2004 17:51:07 -0000
- Subject: remote/1835: An error packet in reply to an 'm' packet is not treated as an error
- Reply-to: trini at kernel dot crashing dot org
>Number: 1835
>Category: remote
>Synopsis: An error packet in reply to an 'm' packet is not treated as an error
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Dec 21 17:58:00 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator: trini@kernel.crashing.org
>Release: gdb-6.1 and gdb-6.3 at least
>Organization:
>Environment:
Debian/testing, Debian/unstable
>Description:
In a remote debugging session (say KGDB from kgdb.sf.net) issuing a backtrace from a breakpoint will result in something like:
Breakpoint 1, sys_sync ()
at /home/trini/work/kernel/pristine/amit-kgdb/linux-2.6.10-rc3/fs/buffer.c:2
95
295 do_sync(1);
#0 sys_sync ()
at /home/trini/work/kernel/pristine/amit-kgdb/linux-2.6.10-rc3/fs/buffer.c:2
95
Sending packet: $md7be5fbc,4#8f...Ack
Packet received: 0040bed7
Sending packet: $md7be5fc0,4#5d...Ack
Packet received: 5f2310c0
#1 0xc010235f in syscall_call () at atomic.h:171
Sending packet: $md7be5fbc,4#8f...Ack
Packet received: 0040bed7
Sending packet: $mc0102358,1#90...Ack
Packet received: ff
Sending packet: $mc0102358,1#90...Ack
Packet received: ff
Sending packet: $mc0102358,1#90...Ack
Packet received: ff
Sending packet: $mc0102358,1#90...Ack
Packet received: ff
Sending packet: $mc0102358,1#90...Ack
Packet received: ff
Sending packet: $md7be5fbc,4#8f...Ack
Packet received: 0040bed7
Sending packet: $md7be5fc4,4#61...Ack
Packet received: 14feffbf
Sending packet: $mbffffe14,8#95...Ack
Packet received: E03
Sending packet: $mbffffe14,7#94...Ack
Packet received: E03
#2 0xbffffe14 in ?? ()
Sending packet: $md7be5fbc,4#8f...Ack
Packet received: 0040bed7
Sending packet: $md7be5fbc,4#8f...Ack
Packet received: 0040bed7
Sending packet: $md7be5fc8,4#65...Ack
Packet received: 04000000
Sending packet: $m4,8#05...Ack
Packet received: E03
Sending packet: $m4,7#04...Ack
Packet received: E03
#3 0x00000004 in ?? ()
Sending packet: $md7be5fbc,4#8f...Ack
Packet received: 0040bed7
Sending packet: $md7be5fbc,4#8f...Ack
Packet received: 0040bed7
Sending packet: $md7be5fcc,4#90...Ack
Packet received: 00000000
Sending packet: $m0,8#01...Ack
Packet received: E03
Sending packet: $m0,7#00...Ack
Packet received: E03
... repeating ...
With gdb-6.0, after the first error packet is seen, the backtrace will stop.
>How-To-Repeat:
Issue a backtrace command for a remote app in conditions where the GDB server should send back an 'E' packet in reply to an 'm' packet.
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: