Re: Tracking a bug in x86-64

> (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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: Tracking a bug in x86-64
  - From: Bongani Hlope <[email protected]>

References:
- Tracking a bug in x86-64
  - From: Bongani Hlope <[email protected]>
- Re: Tracking a bug in x86-64
  - From: Bongani Hlope <[email protected]>
- Re: Tracking a bug in x86-64
  - From: Linus Torvalds <[email protected]>
- Re: Tracking a bug in x86-64
  - From: Bongani Hlope <[email protected]>
- Re: Tracking a bug in x86-64
  - From: Linus Torvalds <[email protected]>

Prev by Date: Re: A Great Idea (tm) about reimplementing NLS.
Next by Date: Re: [PATCH] 3 of 5 IMA: LSM-based measurement code
Previous by thread: Re: Tracking a bug in x86-64
Next by thread: Re: Tracking a bug in x86-64
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]