This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
TUI + gdbserver broken?
- From: Pedro Alves <pedro_alves at portugalmail dot pt>
- To: gdb at sourceware dot org
- Date: Wed, 14 Mar 2007 00:55:40 +0000
- Subject: TUI + gdbserver broken?
Hi,
TUI + gdbserver seems to be broken on head. Can't reproduce when
TUI + native debugging.
main is a simple hello world.
Could this still be related to the recent get_selected_frame
changes? I tried to blindly change all of them in
tui/tui-hooks.c to deprecated_get_selected_frame, but it
didn't fix it.
I also see some nasty extra screen repaints in
tui mode while stepping I didn't see before. Any ideas?
$gdbserver :9999 main
$gdb main.exe
GNU gdb 6.6.50.20070312-cvs
Copyright (C) 2007 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i686-pc-cygwin"...
(gdb) tar rem :9999
Remote debugging using :9999
[New Thread 5340]
[Switching to Thread 5340]
0x7c911231 in ?? ()
(gdb) c
Continuing.
Program exited normally.
(gdb) c
The program is not being run.
----
$gdbserver :9999 main
$gdbtui main
tar rem :9999
Remote debugging using :9999
[New Thread 5612]
[Switching to Thread 5612]
0x7c911231 in ?? ()
(gdb) c
Continuing.
Remote communication error: Software caused connection abort.
(gdb) c
Continuing.
putpkt: write failed: Software caused connection abort.