From: David Highley <dhighley@highley-recommended.com>
To: gdb@sources.redhat.com
Subject: RedHat Advanced Server 3 and thread debugging
Date: Sat, 17 Sep 2005 03:00:00 -0000 [thread overview]
Message-ID: <200509170259.j8H2xtPb029425@douglas.highley-recommended.com> (raw)
We have implemented and a large application that is built on many
different operating systems with platform native tools. For Linux we use
the RedHat Advanced Server 3 update 3 platform. Development has a lot of
problems debugging threaded applications on this platform.
We build our applications static. Today one of the developers rebuilt
an application using the apparently undocumented option -rdynamic and
found that he was able to get better trace back information. Then
dynamic link was done and he found that still more debugging
information was available. Another thing they noticed was instead of one
pid per thread there was just one pid. Which now leads us to wonder if
we have the same thread model in a static link and a dynamic link.
Can anyone shed some intelligent light on these observations. For a
concept that is so widely used it seems difficult to get very good
information on any platform.
next reply other threads:[~2005-09-17 3:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-17 3:00 David Highley [this message]
[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
2005-09-19 20:41 ` Daniel Jacobowitz
2005-09-19 20:42 Ajay Patel
2005-09-19 20:52 Ajay Patel
2005-09-19 20:55 ` Daniel Jacobowitz
2005-09-19 22:45 Ajay Patel
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=200509170259.j8H2xtPb029425@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).