From: Daniel Jacobowitz <drow@mvista.com>
To: Smita <smita@cse.ucsc.edu>
Cc: gdb@sources.redhat.com
Subject: Re: gdb's communication to a process/libgdb?
Date: Wed, 16 Apr 2003 20:04:00 -0000 [thread overview]
Message-ID: <20030416200351.GA5152@nevyn.them.org> (raw)
In-Reply-To: <Pine.GSO.4.44.0304161255130.12775-100000@sundance.cse.ucsc.edu>
On Wed, Apr 16, 2003 at 12:59:14PM -0700, Smita wrote:
> Hi,
> I am spawing a gdb process from my process and feeding to gdb an input
> script.
> I want the parent process to be able to control this gdb process. For this
> to happen, I want to communicate to the parent process that a breakpoint
> has occurred when gdb stops at a breakpoint? Is it possible to to this?
> There is something called libgdb. I am not sure if that can be used for
> this purpose.
>
> Any feedback on this would be greatly appreciated.
You should probably be reading the documentation for "MI". Check the
manual, available online under http://sources.redhat.com/gdb/.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-04-16 20:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-16 18:18 gdb refuses to 'break' Markus Brandner
2003-04-16 19:51 ` return type of a fucntion Smita
2003-04-16 19:59 ` gdb's communication to a process/libgdb? Smita
2003-04-16 20:04 ` Daniel Jacobowitz [this message]
2003-04-16 22:07 ` libgdb Smita
2003-04-16 23:58 ` is libgdb okay to use? Smita
2003-04-17 1:44 ` libgdb Elena Zannoni
2003-04-17 2:06 ` libgdb Smita
2003-04-17 2:12 ` finish implementation Smita
2003-04-17 12:57 ` libgdb Elena Zannoni
2003-04-17 2:11 ` finish for nested function calls Smita
2003-04-17 3:37 ` return type of a fucntion Peter Barada
2003-04-17 9:13 ` gdb refuses to 'break' Markus Brandner
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=20030416200351.GA5152@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=smita@cse.ucsc.edu \
/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