This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
remote/2198: GDB remote debugging seems to be broken.
- From: samueldotj at gmail dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 13 Nov 2006 06:06:33 -0000
- Subject: remote/2198: GDB remote debugging seems to be broken.
- Reply-to: samueldotj at gmail dot com
>Number: 2198
>Category: remote
>Synopsis: GDB remote debugging seems to be broken.
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Mon Nov 13 06:08:01 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator: Samuel
>Release: 5.2.1
>Organization:
>Environment:
Cygwin Windows-XP
>Description:
I am trying use GDB for remote debugging. GDB gets the hardcoded breakpoint signal and stops. However I am unable to read or write any memory value because GDB always sends only the last two hexa decimals of the address whenever a print or set command is issued. Below I have attached a example.
I am using the sample i386-stub.c in the grub source.
The latest version of GDB in cygwin and mingw are crashing when I open a remote debugging session.
The serial connection is ok. I tested with HyperTerminal.
Please let me know if I have to add more details.
----------------------------------------------------------
(gdb) printf "%X\n", &wel
C0053F88
(gdb) printf "%X", wel
Sending packet: $m88,4#3d...Ack
Packet received: 17e800f0
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: