Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: kceiwH <kceiwh@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: errors in GDB reading symbols
Date: Mon, 03 Aug 2009 16:53:00 -0000	[thread overview]
Message-ID: <m3tz0oltyo.fsf@fleche.redhat.com> (raw)
In-Reply-To: <97234C41-9CA5-4A2C-89BA-6B54256D8B81@gmail.com> (kceiwh@gmail.com's message of "Sat\, 1 Aug 2009 17\:38\:15 -0400")

>>>>> ">" == kceiwH  <kceiwh@gmail.com> writes:

>> I try to write a program to convert a line number of the source code
>> to the corresponding memory address. The program will link to libgdb,
>> libbfd, libiberty, libopcodes, which are generated when you compile
>> GDB.

I think we would prefer that you not use libgdb.  Nobody has worked on
turning gdb into a library in many years.  What you see in the tree is
not even the minimum necessary to get that to work.

I'd like to propose that we get rid of libgdb.a entirely.
I think all it does is slow down the build.

Tom


  parent reply	other threads:[~2009-08-03 16:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-01 21:38 kceiwH
2009-08-02 23:45 ` kceiwH
2009-08-03 16:53 ` Tom Tromey [this message]
2009-08-03 17:01   ` Daniel Jacobowitz
2009-08-03 20:47     ` Baurzhan Ismagulov
2009-08-04 14:33     ` Tom Tromey
2009-08-04 14:46       ` Daniel Jacobowitz
2009-08-04 14:47         ` Daniel Jacobowitz
2009-08-04 14:52       ` Jonas Maebe
2009-08-04 14:55         ` Daniel Jacobowitz
2009-08-06 17:09         ` Tom Tromey
2009-08-06 21:00           ` Jonas Maebe
2009-08-07 16:24             ` Daniel Jacobowitz
2009-08-07 20:48 Marco van de Voort
2009-08-11 21:00 ` Tom Tromey
2009-08-12  0:56   ` Paul Pluzhnikov
2009-08-21 17:33     ` Tom Tromey

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=m3tz0oltyo.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=kceiwh@gmail.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