From: Daniel Jacobowitz <drow@mvista.com>
To: Carlo Wood <carlo@alinoe.com>
Cc: gdb@sources.redhat.com
Subject: Re: Is this information correct?
Date: Mon, 27 May 2002 11:07:00 -0000 [thread overview]
Message-ID: <20020527180721.GC5523@branoic.them.org> (raw)
In-Reply-To: <20020527142006.A23953@alinoe.com>
On Mon, May 27, 2002 at 02:20:06PM +0200, Carlo Wood wrote:
> In the next release of libcwd (http://libcwd.sourceforge.net)
> I will add the information below.
>
> Because this will reach a few hunderd C++ developers, I wanted
> to check with you if this information is correct in your eyes.
> Any improvement is welcomed.
>
> -------
> A core dump produced by a kernel 2.4 does not
> contain enough information for gdb to debug all
> threads. Only the core dumping thread is dumped
> and the other threads continue to run for a while.
> There exists a kernel patch written by Intel/IBM
> that fixes this problem; please read
> http://www.apachelabs.org/lkml/200203.mbox/%3c20020315170726.A3405@in.ibm.com%3e
> or
> http://www.uwsg.iu.edu/hypermail/linux/kernel/0203.1/0963.html
This part's fine.
> You are strongly advised to use gdb 5.2 for multithreaded
> debugging; however, it may be possible that the released
> gdb 5.2 is not capable of reading the debug information
> that is used by gcc 3.1, I heard (libcwd needed to be fixed
> too), the latest CVS version of gdb works though.
What's this part about though? I think it's really referring to gdb
5.1 instead. 5.2 should be fine.
> Be aware that gdb does hardly support namespaces and
> will therefore frequently not find types or variables
> in namespaces. It doesn't look like that this will be
> fixed very soon (2002-05-27).
> --------
>
> --
> Carlo Wood <carlo@alinoe.com>
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-05-27 18:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-27 5:20 Carlo Wood
2002-05-27 11:07 ` Daniel Jacobowitz [this message]
2002-05-27 17:09 ` Carlo Wood
2002-05-27 21:30 ` Carlo Wood
2002-05-28 18:05 ` Andrew Cagney
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=20020527180721.GC5523@branoic.them.org \
--to=drow@mvista.com \
--cc=carlo@alinoe.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