linux-kernel - Re: [PATCH 1/1] x86: Add process memory layout to coredump file

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: <20111212210328.GA29248@host2.jankratochvil.net>
Date:	Mon, 12 Dec 2011 22:03:28 +0100
From:	Jan Kratochvil <jan.kratochvil@...hat.com>
To:	t cheney <cdmalord@...il.com>
Cc:	gdb <gdb@...rceware.org>, linux-kernel@...r.kernel.org,
	viro@...iv.linux.org.uk, linux-fsdevel@...r.kernel.org,
	crash-catcher@...ts.fedorahosted.org
Subject: Re: [PATCH 1/1] x86: Add process memory layout to coredump file

On Sun, 11 Dec 2011 15:10:00 +0100, t cheney wrote:
> This patch just add memory layout(same as /proc/pid/maps) to
> coredump file. The layout is appended to corenote segment with
> flag NT_MAPS=7.

FYI this has been solved by ABRT - Automated Bug-Reporting Tool
	https://fedorahosted.org/abrt/
	(it is distro-neutral despite its homepage)

Core file is there a subdirectory where the core file is just one of the many
associated files:
/var/spool/abrt/ccpp-*:
	abrt_version analyzer architecture cmdline component coredump count
	dso_list environ executable hostname kernel maps os_release package
	pid pwd reason time uid username uuid var_log_messages

More info files are being continually added, such as /proc/PID/fd{,info}/
mapping at the crash dump time etc.  You would need to add many more core file
notes to make the core files useful for later analysis.


Regards,
Jan
--
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/