linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kip Macy <kmacy@netapp.com>
To: Elan Feingold <efeingold@mn.rr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Multithreaded core dumps
Date: Wed, 29 Aug 2001 22:50:13 -0700 (PDT)	[thread overview]
Message-ID: <Pine.GSO.4.10.10108292242080.10391-100000@cranford-fe.eng.netapp.com> (raw)
In-Reply-To: <000c01c13113$91d7c060$0400000a@gorilla>

> 
> 0. Am I wrong or confused about the state of postmortem multithreaded
> debugging under Linux?

At least as of mid-2.2 series this was certainly my experience. It was
very frustrating that the thread/process that dumped core was not the one
that dereferenced a bad pointer/failed an assert but the process group
leader.

> 
> 2. If this is simply something that nobody is working on because other
> things are more interesting, can anybody give me a few pointers on where
> to start?
> 

I am inclined to believe that that is the case. Unfortunately, I have no
advice to give - but I am writing because I think that it would be neat if
you have the time and the inclination for you to document your findings as
you progress and put them on the web. 

			-Kip


  reply	other threads:[~2001-08-30  5:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-30  5:21 Multithreaded core dumps Elan Feingold
2001-08-30  5:50 ` Kip Macy [this message]
2001-08-30  8:24   ` Alan Cox
2001-08-30  9:03     ` Alexander Viro
2001-08-30  9:12       ` Alan Cox
2001-08-30 10:08         ` Alexander Viro
2001-08-30  9:33       ` David S. Miller
2001-08-30  8:16 ` Multithreaded core dumps (CLONE_THREAD and elf) Terje Eggestad
2001-08-30  9:19   ` Andreas Dilger

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=Pine.GSO.4.10.10108292242080.10391-100000@cranford-fe.eng.netapp.com \
    --to=kmacy@netapp.com \
    --cc=efeingold@mn.rr.com \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).