linux-kernel - TLS info and core files?

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: <20070327092041.40947947@tweety>
Date:	Tue, 27 Mar 2007 09:20:41 -0400
From:	Tom Horsley <tom.horsley@...r.com>
To:	linux-kernel@...r.kernel.org
Cc:	bugsy <bugsy@...r.com>
Subject: TLS info and core files?

As a debugger developer, I find it quite handy when debugging
a real process to use the PTRACE_GET_THREAD_AREA or
PTRACE_GET_ARCH_PRCTL calls to dig up pthread IDs without
having to know too much about the internals of the pthread
library. (It would be even handier if the info was more
consistent across architectures :-).

In a core file, that information has all disappeared.

Should core files have NOTE entries added for some sort of
thread local storage info to be recorded? (Whatever the
kernel happens to know that won't be accessible anymore
after the process is gone, which would probably vary
from architecture to architecture.)
-
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/