public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: David Highley <dhighley@highley-recommended.com>
Cc: gdb@sources.redhat.com
Subject: Re: GDB problem with statically linked application
Date: Tue, 20 Sep 2005 19:59:00 -0000	[thread overview]
Message-ID: <20050920195910.GA28801@nevyn.them.org> (raw)
In-Reply-To: <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

  reply	other threads:[~2005-09-20 19:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1127244795.20581@horse.he.net>
2005-09-20 19:53 ` David Highley
2005-09-20 19:59   ` Daniel Jacobowitz [this message]
2005-09-20 18:50 Ajay Patel
2005-09-20 19:08 ` David Highley
2005-09-20 19:14   ` Daniel Jacobowitz

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=20050920195910.GA28801@nevyn.them.org \
    --to=drow@false.org \
    --cc=dhighley@highley-recommended.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).