This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: GDB problem with statically linked application
- From: Daniel Jacobowitz <drow at false dot org>
- To: David Highley <dhighley at highley-recommended dot com>
- Cc: gdb at sources dot redhat dot com
- Date: Tue, 20 Sep 2005 15:59:10 -0400
- Subject: Re: GDB problem with statically linked application
- References: <1127244795.20581@horse.he.net> <200509201952.j8KJqnaS018386@douglas.highley-recommended.com>
On Tue, Sep 20, 2005 at 12:52:49PM -0700, David Highley wrote:
> "Ajay Patel wrote:"
> >
> >
> > > We still see multiple pid's for static linked applications and not for
> > > dynamically linked applications. We are now in the process of rebuilding
> > > and running tests on our applications.
> >
> > I also saw this. I did not investigated much.
> > I think this may be glibc bug. This shows up
> > when you use linux-threads. If you use NPTL
> > it does go away.
>
> The insidious part of this is our small test code will execute even if
> you use the incorrect "-lpthread" flag with dynamic linking. So the
> remaining question to be figured out is whether the thread model is the
> same between the static and dynamic links. Do we get NPTL threads in
> both cases? We might be able to tell with the nm command.
For the second or third time: this is not the appropriate list to
discuss this particular problem. It is completely dependent upon your
distributor, not the GNU toolchain.
In general, most distributions which ship both ship LinuxThreads
(because it is more portable) as the static default. They also publish
in their documentation instructions on how to statically link with
NPTL. The distributor's documentation is your best reference.
--
Daniel Jacobowitz
CodeSourcery, LLC