From: "Ajay Patel" <ajayp@kymasys.com>
To: Mark Kettenis
<mark.kettenis@xs4all.nl>,pkoning@equallogic.com,dhighley@highley-recommended.com,
gdb@sources.redhat.com
Subject: Re: RedHat Advanced Server 3 and thread debugging
Date: Mon, 19 Sep 2005 20:42:00 -0000 [thread overview]
Message-ID: <1127162560.15892@horse.he.net> (raw)
> 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.
I have tried various combination of glic, kernel
and gdb on different platform. Nothing works for me.
Platform : I386 & PPC
Kernel : 2.6.9, 2.6.11 & 2.6.11-1.1369_FC4.
Glibc : 2.3.4 and 2.3.5 with NPTL.
Gdb : 6.3 and Gdb from Debian CVS.
>
> 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.
The problem is, when brekpoint is encountered in a non-main
thread (or Newly created thread), the GDB terminates with
SIGTRAP.
Thanks
Ajay
next reply other threads:[~2005-09-19 20:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-19 20:42 Ajay Patel [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-19 22:45 Ajay Patel
2005-09-19 20:52 Ajay Patel
2005-09-19 20:55 ` Daniel Jacobowitz
[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-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=1127162560.15892@horse.he.net \
--to=ajayp@kymasys.com \
--cc=dhighley@highley-recommended.com \
--cc=gdb@sources.redhat.com \
--cc=mark.kettenis@xs4all.nl \
--cc=pkoning@equallogic.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).