From: "Kei Sakamoto" <sakamoto.kei@renesas.com>
To: "Andreas Schwab" <schwab@suse.de>
Cc: <gdb@sources.redhat.com>
Subject: Re: What creates corefiles?
Date: Mon, 25 Oct 2004 15:26:00 -0000 [thread overview]
Message-ID: <01f101c4ba78$6ce86d30$5169910a@E5A02646> (raw)
In-Reply-To: <jemzybm8ui.fsf@sykes.suse.de>
Thank you for your suggestion. I'll look into the kernel.
Kei Sakamoto
From: "Andreas Schwab" <schwab@suse.de>
To: "Kei Sakamoto" <sakamoto.kei@renesas.com>
Cc: <gdb@sources.redhat.com>
Sent: Monday, October 25, 2004 6:43 PM
Subject: Re: What creates corefiles?
"Kei Sakamoto" <sakamoto.kei@renesas.com> writes:
> So I'd like to check whether corefiles are correct. But I don't
> know what creates corefiles. (Linux kernel? GLIBC?)
It's the kernel.
> Would anyone suggest which source files I should look into?
Look at fs/binfmt_elf.c in the kernel sources.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
prev parent reply other threads:[~2004-10-25 9:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-25 12:53 Kei Sakamoto
2004-10-25 15:22 ` Andreas Schwab
2004-10-25 15:26 ` Kei Sakamoto [this message]
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='01f101c4ba78$6ce86d30$5169910a@E5A02646' \
--to=sakamoto.kei@renesas.com \
--cc=gdb@sources.redhat.com \
--cc=schwab@suse.de \
/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