Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: jdavin@cmu.edu, gdb@sources.redhat.com
Subject: Re: gdb not working with older glibc
Date: Tue, 11 Nov 2003 16:39:00 -0000	[thread overview]
Message-ID: <20031111163931.GA12790@nevyn.them.org> (raw)
In-Reply-To: <3FB10EFC.6050001@redhat.com>

On Tue, Nov 11, 2003 at 11:31:56AM -0500, Andrew Cagney wrote:
> >Well that pretty much was the exact output.
> >Here's the version info too:
> >
> >GNU gdb 6.0
> >Copyright 2003 Free Software Foundation, Inc.
> >GDB is free software, covered by the GNU General Public License, and you
> >are
> >welcome to change it and/or distribute copies of it under certain
> >conditions.
> >Type "show copying" to see the conditions.
> >There is absolutely no warranty for GDB.  Type "show warranty" for
> >details.
> >This GDB was configured as "i686-pc-linux-gnu"...
> 
> Sigh.  More recent GDB's print out the libthread_db that was loaded 
> here.  Guess that didn't get into 6.0.

Nope.  (I'm still trying to figure out a way to make the output message
less ugly.  I'm thinking about just sticking a \n in front of it?)

> >(gdb) run
> >Starting program:
> >/path/(name-omitted)
> >
> >Program received signal SIG32, Real-time event 32.
> >0x0811c7f6 in __sigsuspend (set=0xbffff380) at
> >../sysdeps/unix/sysv/linux/sigsuspend.c:45
> >45      ../sysdeps/unix/sysv/linux/sigsuspend.c: No such file or
> >directory.
> >        in ../sysdeps/unix/sysv/linux/sigsuspend.c
> >Current language:  auto; currently c
> >
> >And for gdb 6.0 working, it's just the same thing without the error/crash.
> 
> Anyway, this is the problem:
> 
> >>The problem is most likely that GDB is loading the lated libthread_db
> >>and that library is refusing to debug the older glibc.
> >>
> >>Perhaphs there should be a "set libthread_db ... command?"
> 
> you need to force GDB into loading the correct libthread_db library.  I 
> guess using something like LD_LIBRARY_PATH?  Or perhaphs overriding 
> gdb/thread-db.c:#define LIBTHREAD_DB_SO?

Er, he updated glibc on his system, didn't he?  All of the applications
should be using the same shared linuxthreads object and thus require
the same libthread_db.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2003-11-11 16:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-10 19:01 jdavin
2003-11-10 21:01 ` Andrew Cagney
2003-11-10 21:39   ` jdavin
2003-11-11 16:32     ` Andrew Cagney
2003-11-11 16:39       ` Daniel Jacobowitz [this message]
2003-11-11 18:21       ` jdavin

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=20031111163931.GA12790@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=ac131313@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=jdavin@cmu.edu \
    /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