From: Daniel Jacobowitz <dan@debian.org>
To: Kumaraswamy Mudide <kumara_mudide@yahoo.com>
Cc: linux-mips@linux-mips.org
Subject: Re: gdb info threads with core files
Date: Tue, 28 Mar 2006 17:37:57 -0500 [thread overview]
Message-ID: <20060328223757.GB12609@nevyn.them.org> (raw)
In-Reply-To: <20060328222835.93334.qmail@web31904.mail.mud.yahoo.com>
On Tue, Mar 28, 2006 at 02:28:35PM -0800, Kumaraswamy Mudide wrote:
> Hi Everyone,
>
> We are using linux 2.4.25 and gdb 6.4, info threads with the core files always shows only single thread. This threads is same as to which we have sent segv or abort signal.
>
> bt and info reg seems to be working fine. but not info threads.
>
> Any idea??
Then your kernel probably does not support multithreaded core dumping.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-03-28 22:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-28 22:28 gdb info threads with core files Kumaraswamy Mudide
2006-03-28 22:37 ` Daniel Jacobowitz [this message]
2006-03-28 22:56 ` Kumaraswamy Mudide
2006-03-29 15:45 ` Kumaraswamy Mudide
2006-03-29 15:45 ` Kumaraswamy Mudide
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=20060328223757.GB12609@nevyn.them.org \
--to=dan@debian.org \
--cc=kumara_mudide@yahoo.com \
--cc=linux-mips@linux-mips.org \
/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