This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Fwd: Question regarding core dump debugging using gdb on armv4
- From: Pedro Alves <palves at redhat dot com>
- To: Abhijit Ray Chaudhury <abhijit dot ray dot chaudhury at gmail dot com>
- Cc: gdb at sourceware dot org
- Date: Mon, 08 Apr 2013 17:56:24 +0100
- Subject: Re: Fwd: Question regarding core dump debugging using gdb on armv4
- References: <CAACKNgWzC9t=OeO1N=EpoDGHtb5L6HssehYmEBJEuLC71O9hmQ at mail dot gmail dot com> <CAACKNgVpk_JE_vOnB+3D3XVh=mE7Gww8nKpWQ3JOYwzmnXsApQ at mail dot gmail dot com> <CAACKNgXh91dW5P23pA5fwR+qSUHXbuzP1R9qMKiGbUg=qjsLTg at mail dot gmail dot com> <515D459A dot 9080802 at redhat dot com> <CAACKNgW8d3qiYb1ao6+V3XpOJc7hnxY9oDAhUPD5LXjoxEYeyQ at mail dot gmail dot com>
On 04/08/2013 04:27 AM, Abhijit Ray Chaudhury wrote:
> From your answer it looked like I need lot of ELF parsing , so I think
> I need to invoke user level program when core dump happens.
No big elf parsing, just browsing through some
structures:
OS auxiliary vector (which the kernel has access to)
-> find PT_DYNAMIC program header
-> find DT_DEBUG dyntag
-> find r_debug
-> follow r_debug.
But I definitely agree a user level program would be better than
hacking this in the kernel, which IMO wouldn't be likely accepted
upstream.
--
Pedro Alves