From: Paul Breed <pbreed@netburner.com>
To: gdb@sources.redhat.com
Subject: GDB Remote network strangeness...
Date: Tue, 28 Jun 2005 23:58:00 -0000 [thread overview]
Message-ID: <6.0.0.22.2.20050628165217.0252ce50@mail.netburner.com> (raw)
I'm using cross GDB with a remote stub over TCP.
When I use it on a windows XP machine with hardware serial ports it works fine.
When I use it on an XP laptop with a USB serial port adaptor it does not work.
If I unplug the usb serial adaptor it does work.
The strange part is that I'm using a TCP connection, gdb is not using the
serial port at all,
yet it seams that the remote protocol stuff (origionally written for serial
I/O)is still doing something
with the serial subsystem when in TCP mode.
I've looked at the remote target stuff and it looks fairly tightly coupled
to the
serial system with a hack like bypass to use TCP when TCP is specified.
Anyone have any ideas on how to remove this serial glich
I'm about to start tearing into the code and am open for suggestions as to
where to look.
Paul
next reply other threads:[~2005-06-28 23:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-28 23:58 Paul Breed [this message]
2005-06-29 0:58 ` Daniel Jacobowitz
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=6.0.0.22.2.20050628165217.0252ce50@mail.netburner.com \
--to=pbreed@netburner.com \
--cc=gdb@sources.redhat.com \
/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