| 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
| ||
|
Date: Tue, 02 Jan 2007 20:57:21 -0800 (PST) From: David Miller <davem@...emloft.net> To: dan@...ian.org Cc: linux-kernel@...r.kernel.org Subject: Re: Contents of core dumps From: Daniel Jacobowitz <dan@...ian.org> Date: Tue, 2 Jan 2007 21:02:28 -0500 > On Thu, Apr 06, 2006 at 10:18:07PM -0700, David S. Miller wrote: > > How about something like the following patch? If it's executable > > and not written to, skip it. This would skip the main executable > > image and all text segments of the shared libraries mapped in. > > I've been going through GDB test failures (... again...) and I'm down > to a respectably small number on x86_64, but this is one of the > remaining ones. I don't suppose there's been any change since we > discussed this in April? Not to my knowledge. > Does Linux need knobs for this? I don't think so. The current behavior is very non-intuitive. As a person who hacks gdb, the kernel, and the interactions between them extensively, it took even me quite a while to track down this problem. Imagine some less skilled person trying to analyze a core dump expecting the necessary information to be there and being unable to figure out why? So I'd say we should just put this change in, as-is. It fixes bugs, and in all the time that has passed since my initial posting there has not been any serious dissent. - 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/
Powered by blists - more mailing lists