Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Gary Thomas <gary@chez-thomas.org>
To: Vinayak P Risbud <vinayak@multitech.co.in>
Cc: eCos Discussion <ecos-discuss@sources.redhat.com>,
	gdb <gdb@sources.redhat.com>
Subject: Re: [ECOS] remote debugging
Date: Mon, 22 Jul 2002 09:43:00 -0000	[thread overview]
Message-ID: <1027356137.25328.31.camel@hermes.chez-thomas.org> (raw)
In-Reply-To: <3D3C33F9.54517685@multitech.co.in>

On Mon, 2002-07-22 at 10:34, Vinayak P Risbud wrote:
>         Hi,
>             I am trying to use remote debugging using LAN (Tcp/Ip) on
> Redboot
>             What I understood till now is,
>                     1.  the main polls net_io_test function during idle
> time
>                     2.  The function net_io_test checks for
>                                         tcp_sock.state == _ESTABLISHED
>                     3.   If established, the control calls
> net_io_assume_console
>                          to setup debug channel.

More than that - at this point, all "console" I/O to RedBoot now goes
through the TCP/IP connection.

> 
>                 But,  after this, how the flow goes,  I am not able to
> trace.
>                 my gdb client on remote PC sends $Hc-1#09 command,
>                 over tcp/ip link.
>                 I am not able to trace, where and how exactly this gdb
>                 command is read and processed (i.e trap is generated ?)

As soon as RedBoot sees a "$" at the start of a command line, it 
switches to GDB (via a call to 'breakpoint()').  This happens whether 
you are using serial or network I/O.  GDB will then continue to use the
network connection for it's I/O to the target device.



      reply	other threads:[~2002-07-22 16:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-22  9:35 Vinayak P Risbud
2002-07-22  9:43 ` Gary Thomas [this message]

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=1027356137.25328.31.camel@hermes.chez-thomas.org \
    --to=gary@chez-thomas.org \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=vinayak@multitech.co.in \
    /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