From: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: Segmentation fault details?
Date: Mon, 11 Aug 2008 09:35:42 +0100 [thread overview]
Message-ID: <g7otku$h3o$1@ger.gmane.org> (raw)
In-Reply-To: ac94cb270808102355o1413f46ehcddb82ae69458c0d@mail.gmail.com
Wang Yi wrote:
> Hi, all!
>
> I'd like to know some details about segmentation fault.
> What I mean is when a program accesses invalid memory area, it will
> get a SIGSEGV signal from kernel, and a message "Segmentation fault".
>
> I also find that dmesg can show we something like this:
> ProgramName[Pid]: segfault at xxxx eip xxxx esp xxxx error x
> It is useful and provides the first-step information for further
> debug/analysis.
>
> My question is how dmesg gets the information, and if there are any
> "decent" way to get this and maybe more information(An "indecent" way
> I came to is grep dmesg)
> so that I can perform some basic auto analysis.
>
> Thank you.
>
> Leo
Core dumps.
You might also like to look at Ubuntu's "apport" bug reporting tool. IIRC
the necessary kernel support is now in mainline. I believe it provides the
option to dump core by piping it through an arbitrary program. The aim of
apport is to capture these core dumps, notify the user, and give them the
option to submit it to the Ubuntu developers.
One advantage of this pipe technique is that you don't need to search the
filesystem for core files. (They're dumped in the current directory, but
you may not know what directory the program was in when it crashed).
Alan
next prev parent reply other threads:[~2008-08-11 8:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ac94cb270808102334m1cc2c3a1n45202072d309927c@mail.gmail.com>
[not found] ` <ac94cb270808102337i5febf70fkb6d1f27f71cafb34@mail.gmail.com>
2008-08-11 6:55 ` Segmentation fault details? Wang Yi
2008-08-11 8:35 ` Alan Jenkins [this message]
2008-08-11 8:36 ` Alan Jenkins
[not found] <aZzy0-8hH-13@gated-at.bofh.it>
[not found] ` <aZzy0-8hH-15@gated-at.bofh.it>
[not found] ` <aZzxZ-8hH-11@gated-at.bofh.it>
2008-08-23 20:23 ` Bodo Eggert
2008-08-24 3:26 ` Calvin Walton
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='g7otku$h3o$1@ger.gmane.org' \
--to=alan-jenkins@tuffmail.co.uk \
--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