public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@muc.de>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Bongani Hlope <bonganilinux@mweb.co.za>,
	Andrew Morton <akpm@osdl.org>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Arjan van de Ven <arjan@infradead.org>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: Tracking a bug in x86-64
Date: 16 Jun 2005 04:02:47 +0200
Date: Thu, 16 Jun 2005 04:02:47 +0200	[thread overview]
Message-ID: <20050616020247.GA27608@muc.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0506151740110.8487@ppc970.osdl.org>

> (It would be even better to see that for one of the processes that tends 
> to core-dump, like "cc1", but that would require you to catch it, probably 
> by doign ^Z at just the right time)

iirc gdb can extract that information from a core dump.
if not readelf -a probably can. 

-Andi

  reply	other threads:[~2005-06-16  2:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-13 20:59 Tracking a bug in x86-64 Bongani Hlope
2005-06-13 21:23 ` Andi Kleen
2005-06-13 21:39 ` Bongani Hlope
2005-06-13 21:48   ` Andi Kleen
2005-06-14 15:36   ` Linus Torvalds
2005-06-14 20:27     ` Andrew Morton
2005-06-14 21:19       ` Bongani Hlope
2005-06-15 22:20       ` Bongani Hlope
2005-06-15 22:39         ` Linus Torvalds
2005-06-15 23:39           ` Bongani Hlope
2005-06-16  0:46             ` Linus Torvalds
2005-06-16  2:02               ` Andi Kleen [this message]
2005-06-16  6:49                 ` Bongani Hlope
     [not found]             ` <xfkll4lfy41.fsf@uxkm53.drewag.de>
2005-07-05 19:52               ` Bongani Hlope
2005-07-05 21:12                 ` Andrew Morton
2005-07-06  6:34                   ` Arjan van de Ven
2005-07-06 18:20                     ` Bongani Hlope

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=20050616020247.GA27608@muc.de \
    --to=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=bonganilinux@mweb.co.za \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=torvalds@osdl.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