From: jacques <jacqueslenormand@sympatico.ca>
Cc: gdb@sources.redhat.com
Subject: libgdb
Date: Wed, 02 Jul 2003 07:13:00 -0000 [thread overview]
Message-ID: <3F0230A3.6090101@sympatico.ca> (raw)
In-Reply-To: <00df01c33ff2$361e0b40$0a00a8c0@nkelseyhome>
Hello,
I'm currently working on a new debugger, and I want to base it on
libgdb. However, finding documentation about libgdb, or even finding
libgdb itself, has proved a daunting task. My understanding is that
libgdb is simply a library containing all the high level functions of
gdb, but let's me call them inside my code. Is libgdb rebuilt everytime
a new gdb comes out? where can i find more information about
libgdb(google gives me 2 manuals, both very very sparse on any
information), and where would I get the latest libgdb?
--Jacques
next prev parent reply other threads:[~2003-07-02 7:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-01 1:20 Frame handling Jafa
2003-07-01 3:42 ` Daniel Jacobowitz
2003-07-01 4:18 ` Andrew Cagney
[not found] ` <redirect-6800274@silicondust.com>
2003-07-01 5:13 ` Jafa
2003-07-01 12:58 ` Andrew Cagney
2003-07-01 14:09 ` Daniel Jacobowitz
2003-07-01 14:57 ` Andrew Cagney
[not found] ` <redirect-6810110@silicondust.com>
2003-07-01 17:00 ` Jafa
2003-07-02 7:13 ` jacques [this message]
[not found] ` <redirect-6810084@silicondust.com>
2003-07-01 16:14 ` Jafa
2003-07-01 17:59 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2007-11-02 16:45 libgdb Matthew Hall
2007-11-02 16:58 ` libgdb Daniel Jacobowitz
2007-11-02 20:30 ` libgdb Stan Shebs
2003-04-16 19:59 gdb's communication to a process/libgdb? Smita
2003-04-16 22:07 ` libgdb Smita
2003-04-17 1:44 ` libgdb Elena Zannoni
2003-04-17 2:06 ` libgdb Smita
2003-04-17 12:57 ` libgdb Elena Zannoni
2002-11-22 14:26 libgdb a2782
2002-11-22 14:52 ` libgdb Keith Seitz
2002-11-22 15:03 ` libgdb Joel Brobecker
2002-10-23 22:46 libgdb Satya
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=3F0230A3.6090101@sympatico.ca \
--to=jacqueslenormand@sympatico.ca \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).