linux-kernel - Segmentation fault details?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <ac94cb270808102355o1413f46ehcddb82ae69458c0d@mail.gmail.com>
Date:	Mon, 11 Aug 2008 14:55:13 +0800
From:	"Wang Yi" <leonidwang@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Segmentation fault details?

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