public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
* Remote Debugging Revisited
@ 2000-06-12  6:26 Michael Crowe
  2000-06-12  6:36 ` Keith Seitz
  0 siblings, 1 reply; 2+ messages in thread
From: Michael Crowe @ 2000-06-12  6:26 UTC (permalink / raw)
  To: Insight

I hope you all could give me a hand with a little problem I'm having.
This may be more of a gdb thing than insight, but I'll try anyway.  I am
trying to set up remote debugging over ethernet.  I start up gdb server
with the host name and port number and my executable program, test, as
arguments, like this:

gdbserver beru:2345 test

Then I fire up gdb(i.e. Insight) on my host and try to use target remote
from the gdb console to connect, the target display then a line that
says "remote debugging using beru:2345.  All of this seems good, but
then when I get to the Insight window, I cannot list the program or run
it, or anything.

If anyone has any thoughts, please help me.

Thanks,
Michael E Crowe
mike@timesys.com

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Remote Debugging Revisited
  2000-06-12  6:26 Remote Debugging Revisited Michael Crowe
@ 2000-06-12  6:36 ` Keith Seitz
  0 siblings, 0 replies; 2+ messages in thread
From: Keith Seitz @ 2000-06-12  6:36 UTC (permalink / raw)
  To: Michael Crowe; +Cc: Insight

Michael Crowe wrote:
> 
> Then I fire up gdb(i.e. Insight) on my host and try to use target remote
> from the gdb console to connect, the target display then a line that
> says "remote debugging using beru:2345.  All of this seems good, but
> then when I get to the Insight window, I cannot list the program or run
> it, or anything.

The "remote debugging using..." message doesn't really mean much,
unfortunately. This just means that gdb was able to open the specified
transport layer (in your case ethernet connection to your gdbserver). So
we need to get more information.

I recommend running gdb in command line mode (foo-bar-gdb -nw) and
turning on remote debugging (set remotedebug 1). This will give you more
explicit information on what is causing problems for gdb (we hope). If
you're running on unix, you could use tcpdump to see if there is any
communication going on between your host and the remote machine, too.
There is probably something similar for Windows somewhere, but I haven't
a clue what it is or where to get it. (I know of serial sniffers, but
not ethernet.)

Try the remotedebug thing and let us know what gdb says.\x13(What's your
host, again?)
Keith
-- 
Why chat when you can Firetalk?
Firetalk ID: Keith (10320)
www.firetalk.com

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2000-06-12  6:36 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2000-06-12  6:26 Remote Debugging Revisited Michael Crowe
2000-06-12  6:36 ` Keith Seitz

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).