Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Biswapesh Chattopadhyay <biswapesh_chatterjee@tcscal.co.in>
To: GDB List <gdb@sources.redhat.com>
Cc: leiming <blackhorse_linux@sina.com>,
	Anjuta devel <anjuta-devel@lists.sourceforge.net>
Subject: Re: how to use libgdb ?
Date: Wed, 18 Sep 2002 21:08:00 -0000	[thread overview]
Message-ID: <1032408527.1308.5.camel@A5-1686> (raw)
In-Reply-To: <Pine.LNX.4.44.0209181128320.22989-100000@dmfet>

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).

Plug: If you are on Linux, please try out Anjuta CVS - you can debug
Anjuta using Anjuta and the debugger interface is really nice !

Thanks in advance.
Biswa.


> Well,
> there really is no libgdb at this point.
> There has been some talk of one by developers as something they'd
> eventually like to do, but right not there is nothing available.
> 
>    However, the gdb build process (at least on linux) created libgdb.a
> and then builds main.c with that to create gdb.  It is possible to
> create libgdb.so rather than libgdb.a and dynamically link to the new
> library.  It just takes some fiddling with the Makefile that configure
> created.
>    I've not done extensive testing on it, but it seems to work for me.
> If you wanted to build your own app on that, you could get sample usage
> from the main.c file
> 
>    I guess it should be pointed out, though, that the libgdb.so that you
> create is a GPL'd work, so even dynamically linking to it then requires
> that you GPL your application as well.
> 
> Scott Moser
> Software Engineer; Linux Technology Center
> IBM Corp., Austin, Tx
> (512) 838-1533   T/L: 678-1533
> ssmoser@us.ibm.com , internal zip: 9812
> 
> On Wed, 18 Sep 2002, leiming wrote:
> 
> >
> >   hi!
> >   Who has used libgdb to integrate gdb into GUI developement?
> > Can you tell me the detailed step or provide some manual?
> >
> >   Thanks a lot!
> >
> > leiming
> > <blackhorse_linux@sina.com>
> >
> 
> 



  reply	other threads:[~2002-09-19  4:08 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 [this message]
2002-09-19  6:32     ` Daniel Jacobowitz
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=1032408527.1308.5.camel@A5-1686 \
    --to=biswapesh_chatterjee@tcscal.co.in \
    --cc=anjuta-devel@lists.sourceforge.net \
    --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