From: Pedro Alves <pedro_alves@portugalmail.pt>
To: gdb@sourceware.org
Subject: TUI + gdbserver broken?
Date: Wed, 14 Mar 2007 00:58:00 -0000 [thread overview]
Message-ID: <45F7480C.5010207@portugalmail.pt> (raw)
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.
next reply other threads:[~2007-03-14 0:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-14 0:58 Pedro Alves [this message]
2007-03-14 2:29 ` Daniel Jacobowitz
2007-03-17 0:48 ` Pedro Alves
2007-03-19 1:54 ` Pedro Alves
2007-03-14 9:29 ` Denis PILAT
2007-03-14 9:42 ` Pedro Alves
2007-03-14 11:55 ` Denis PILAT
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=45F7480C.5010207@portugalmail.pt \
--to=pedro_alves@portugalmail.pt \
--cc=gdb@sourceware.org \
/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