public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: David Highley <dhighley@highley-recommended.com>
To: gdb@sources.redhat.com
Subject: Re: RedHat Advanced Server 3 and thread debugging
Date: Mon, 19 Sep 2005 20:38:00 -0000	[thread overview]
Message-ID: <200509192038.j8JKcWwh025585@douglas.highley-recommended.com> (raw)
In-Reply-To: <200509191916.j8JJGrrM013515@elgar.sibelius.xs4all.nl>

"Mark Kettenis wrote:"
> 
> > Date: Mon, 19 Sep 2005 14:13:39 -0400
> > From: Paul Koning <pkoning@equallogic.com>
> > 
> >  David> "Ajay Patel wrote:"
> >  >> David,
> >  >> 
> >  >> GDB is broken for statically linked application.  No body has
> >  >> bothered to fix this.
> > 
> >  David> Has the platform/tool world silently decided not to support
> >  David> static builds?  
> > 
> > I think Ajay is confused.  Debugging statically linked applications
> > works just fine; if anything, it's the more reliable case since it is
> > the simpler case.
> > 
> 
> Well, that all depends on what version of the Linux kernel you're
> running, what version of glibc you're running, and of course what
> version of gdb you're using.

Kernel: 2.4.21-27.0.2.ELsmp
Glibc: 2.3.2-95.27
gcc: 3.2.3-42
gdb: 6.1post-1.20040607.17

> It's also important to realize that if you're stripping (parts of)
> your binaries, there's simply not enough information left for gdb to
> produce meaningful backtraces.  If you use -rdynamic, at least there
> is the dynamic symbol table for gdb to use.

We do not strip the executables. But oddly no one has addressed the
original question of whether we get the same thread model between a
static and dynamic link given we see with the ps command multiple pid's
for a static link and one pid for dynamic link.

Then there was a reply that indicated there were patches, but no
furthur information. Do we need to patch the; OS, gcc, ld, gdb, etc.

> Mark
> 

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

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1127149130.20359@horse.he.net>
2005-09-19 18:10 ` David Highley
2005-09-19 18:12   ` Daniel Jacobowitz
2005-09-19 18:13   ` Paul Koning
2005-09-19 19:17     ` Mark Kettenis
2005-09-19 20:38       ` David Highley [this message]
2005-09-19 20:41         ` Daniel Jacobowitz
2005-09-19 22:45 Ajay Patel
  -- strict thread matches above, loose matches on Subject: below --
2005-09-19 20:52 Ajay Patel
2005-09-19 20:55 ` Daniel Jacobowitz
2005-09-19 20:42 Ajay Patel
2005-09-17  3:00 David Highley

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=200509192038.j8JKcWwh025585@douglas.highley-recommended.com \
    --to=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).