From: Daniel Jacobowitz <drow@mvista.com>
To: Biswapesh Chattopadhyay <biswapesh_chatterjee@tcscal.co.in>
Cc: GDB List <gdb@sources.redhat.com>,
leiming <blackhorse_linux@sina.com>,
Anjuta devel <anjuta-devel@lists.sourceforge.net>
Subject: Re: how to use libgdb ?
Date: Thu, 19 Sep 2002 06:32:00 -0000 [thread overview]
Message-ID: <20020919133221.GA17132@nevyn.them.org> (raw)
In-Reply-To: <1032408527.1308.5.camel@A5-1686>
On Thu, Sep 19, 2002 at 09:38:40AM +0530, Biswapesh Chattopadhyay wrote:
> Hi list
>
> I'm one of the developers of Anjuta (http://anjuta.sf.net/), an IDE for
> GNOME. Currently, we are using a spawned subprocess for GDB interaction.
> This works fairly well, but obviously a shared library with a nice (and
> reasoinably stable) API would be very helpful for IDE developers. So, my
> question is: if GDB build process already builds libgdb.a, would any
> patches to make it build a shared libgdb.so be accepted into the main
> tree ? It might be very useful, for example, for gnome-debug, which is
> an upcoming component for debugging applications using a nice GUI
> interface. This might speed up the responsiveness and enable us to do
> more advanced stuff (such as tracing multiple threads simultaneously).
They would probably not be accepted - or useful, since we don't plan to
maintain a stable ABI. What we do maintain is a stable
machine-parseable interface - MI. See the documentation or list
archives for more about that if you're not familiar with it.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-09-19 13:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-17 18:06 leiming
2002-09-18 9:29 ` Scott Moser
2002-09-18 21:08 ` Biswapesh Chattopadhyay
2002-09-19 6:32 ` Daniel Jacobowitz [this message]
2002-09-19 9:02 ` Scott Moser
2002-09-19 12:07 ` Daniel Jacobowitz
2002-09-19 13:48 ` Andrew Cagney
2002-09-19 14:18 ` Joel Brobecker
2002-09-18 18:02 leiming
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=20020919133221.GA17132@nevyn.them.org \
--to=drow@mvista.com \
--cc=anjuta-devel@lists.sourceforge.net \
--cc=biswapesh_chatterjee@tcscal.co.in \
--cc=blackhorse_linux@sina.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