Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Dan Kegel <dank@kegel.com>
To: Dan Kegel <dank@kegel.com>
Cc: gdb@sources.redhat.com
Subject: Re: gdb and glibc-2.2.2?
Date: Fri, 01 Jul 2005 18:34:00 -0000	[thread overview]
Message-ID: <42C58AAA.9060405@kegel.com> (raw)
In-Reply-To: <42C588F5.4040704@kegel.com>

Dan Kegel wrote:
> What's the best version of gdb / gdbserver to use with
> glibc-2.2.2?  I'm hoping the latest gdb is ok.
> 
> I'm finally adding gdb support to my toolchain build script.
> Being greedy, I'm trying the latest gdb, even when building
> with old versions of glibc.  In particular, I'm trying
> to build gdb-6.3 and its gdbserver against glibc-2.2.2.
> Building gdbserver fails with
> 
> thread-db.o(.text+0x43e): In function `thread_db_init':
> gcc-3.4.4-glibc-2.2.2/gdb-6.3/gdb/gdbserver/thread-db.c:323: undefined 
> reference to `td_symbol_list'
> thread-db.o(.text+0x443):gcc-3.4.4-glibc-2.2.2/gdb-6.3/gdb/gdbserver/thread-db.c:326: 
> undefined reference to `td_symbol_list'
> 
> because td_symbol_list was added only as of glibc-2.2.3.
> Now, td_symbol_list is a pretty simple function, and
> is probably easy to backport.  I'll probably give that a shot,
> and build gdbserver static (since my glibc with the
> td_symbol_list backport won't get installed on the target).
> Sound reasonable?

Or, maybe I'll take the lame way out, and just
not build gdbserver for glibc < 2.2.3.
Native gdb is what developers usually prefer
anyway, given enough ram...

but the question about which gdb is recommended
for glibc-2.2.2 systems still stands.
- Dan

-- 
Trying to get a job as a c++ developer?  See http://kegel.com/academy/getting-hired.html


      reply	other threads:[~2005-07-01 18:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-01 18:26 Dan Kegel
2005-07-01 18:34 ` Dan Kegel [this message]

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=42C58AAA.9060405@kegel.com \
    --to=dank@kegel.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