From: Abhijit Ray Chaudhury <abhijit.ray.chaudhury@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: Fwd: Question regarding core dump debugging using gdb on armv4
Date: Mon, 08 Apr 2013 03:54:00 -0000 [thread overview]
Message-ID: <CAACKNgVn9ni5m4x3sX1cYW6ZmyeSAD0aY6tJNsVbU1LmYd-AqQ@mail.gmail.com> (raw)
In-Reply-To: <515D459A.9080802@redhat.com>
Pedro,
In solib-svr4.c function
static CORE_ADDR
elf_locate_base (void) {
...
/* Find DT_DEBUG. */
if (scan_dyntag (DT_DEBUG, exec_bfd, &dyn_ptr)
|| scan_dyntag_auxv (DT_DEBUG, &dyn_ptr))
return dyn_ptr;
/* This may be a static executable. Look for the symbol
conventionally named _r_debug, as a last resort. */
msymbol = lookup_minimal_symbol ("_r_debug", NULL, symfile_objfile);
if (msymbol != NULL)
return SYMBOL_VALUE_ADDRESS (msymbol);
Are you asking me going through this section of the code ?
Thanks,
-Abhijit
On Thu, Apr 4, 2013 at 2:49 PM, Pedro Alves <palves@redhat.com> wrote:
> On 04/04/2013 04:30 AM, Abhijit Ray Chaudhury wrote:
>> Hi ,
>>
>> I am trying to reduce core dump size on target running linux . The
>> processor is armv4 family. I tweak elf_core_dump function of linux
>> kernel 2.6.23.
>>
>> I tweaked the kernel to dump only elf note, registers and stack
>> segments of the running process.
>>
>> But gdb fails to load required shared object files and fails to give
>> the backtraces of the running process.
>>
>> Could you please help me ascertain how gdb loads the required
>> libraries from the core dump. Which ELF section of the core contains
>> the information ?
>
> GDB reads the load map off of structures in the dynamic loader (which runs
> in userspace). The dynamic loader->debugger interface has a 'struct r_debug'
> structure in memory that holds the list of loaded libraries. You need to
> preserve that and whatever it references in the core.
>
> In dynamic executables you can find where r_debug is by consulting
> the DT_DEBUG dyntag, found in the .dynamic section of the executable,
> which in turn can be found in the PT_DYNAMIC program header,
> which is found by scanning the OS auxiliary vector, which the kernel
> has access to. All this can be seen in action in gdb's solib-svr4.c.
> Dumping all of libc's memory may work too..
>
> --
> Pedro Alves
>
next prev parent reply other threads:[~2013-04-08 3:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAACKNgWzC9t=OeO1N=EpoDGHtb5L6HssehYmEBJEuLC71O9hmQ@mail.gmail.com>
[not found] ` <CAACKNgVpk_JE_vOnB+3D3XVh=mE7Gww8nKpWQ3JOYwzmnXsApQ@mail.gmail.com>
2013-04-04 3:30 ` Abhijit Ray Chaudhury
2013-04-04 9:19 ` Pedro Alves
2013-04-08 3:27 ` Abhijit Ray Chaudhury
2013-04-08 16:37 ` Pedro Alves
2013-04-08 16:56 ` Pedro Alves
2013-04-08 3:54 ` Abhijit Ray Chaudhury [this message]
2013-04-08 16:48 ` Pedro Alves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAACKNgVn9ni5m4x3sX1cYW6ZmyeSAD0aY6tJNsVbU1LmYd-AqQ@mail.gmail.com \
--to=abhijit.ray.chaudhury@gmail.com \
--cc=gdb@sourceware.org \
--cc=palves@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox