Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Ramana Radhakrishnan <ramana.radhakrishnan@codito.com>
To: james osburn <jjosburn@hotmail.com>
Cc: gdb@sources.redhat.com
Subject: Re: what are gdbstubs?
Date: Thu, 24 Mar 2005 17:08:00 -0000	[thread overview]
Message-ID: <4242F368.3030509@codito.com> (raw)
In-Reply-To: <BAY13-F12876C581715CF84C78076D8400@phx.gbl>

james osburn wrote:
> what are gdbstubs?

GDB when used with embedded targets requires a "stub" on the 
target side to communicate with for information about the 
debuggee's context. These requests(from gdb) could include 
queries about the status of the register contents on the 
debuggee side and memory conditions. One also needs a stub 
to inform gdb that the debuggee has stopped or has exited / 
allow GDB to attach to the debuggee etc.

(If you were debugging an application on a native i386 / 
linux machine you would be using ptrace and the kernel 
informs the debugger that the debuggee has stopped because 
of the wait sys call ) .

HTH
cheers
Ramana

> thanks
> jim
> 
> <html><DIV></DIV></html>
> 


-- 
Ramana Radhakrishnan
GNU Tools
codito ergo sum (www.codito.com)


  reply	other threads:[~2005-03-24 17:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-24 16:58 james osburn
2005-03-24 17:08 ` Ramana Radhakrishnan [this message]
2005-03-24 22:55   ` james osburn
2005-03-24 23:08     ` Ramana Radhakrishnan
2005-03-24 23:12       ` james osburn
2005-03-24 23:15         ` Ramana Radhakrishnan
2005-03-24 23:25           ` tracing ( was Re: what are gdbstubs?) james osburn
2005-03-24 23:44             ` Ramana Radhakrishnan
2005-03-24 23:47               ` Daniel Jacobowitz
2005-03-24 23:48               ` james osburn
2005-03-24 23:59                 ` Ramana Radhakrishnan
2005-03-25  0:09                   ` Ramana Radhakrishnan

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=4242F368.3030509@codito.com \
    --to=ramana.radhakrishnan@codito.com \
    --cc=gdb@sources.redhat.com \
    --cc=jjosburn@hotmail.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