Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: aristovski@qnx.com (Aleksandar Ristovski)
Cc: gdb@sources.redhat.com
Subject: Re: linkmap from PT_DYNAMIC
Date: Fri, 17 Oct 2008 15:22:00 -0000	[thread overview]
Message-ID: <200810171520.m9HFKcns029400@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <gd89q1$k3h$1@ger.gmane.org> from "Aleksandar Ristovski" at Oct 16, 2008 04:56:33 PM

Aleksandar Ristovski wrote:

> Currently GDB will scan dyntags from dynamic section only 
> (solib-svr4.c:scan_dyntag). However, if the section header 
> does not exist (for example it has been stripped away) then 
> gdb gives up, even though the section will be present in the 
> form of dynamic segment.
> 
> When examining core files when having only a stripped 
> executable (stripped in such a way that it does not contain 
> section headers), gdb will not be able to do much.
> 
> The attached patch will resort to using PT_DYNAMIC to get 
> dynamic section and scan dyntag. The patch will only change 
> default (current) behaviour if bfd_get_section_by_name 
> returns NULL.

Well, the scan_dyntag_auxv routine I added already does
attempt to access PT_DYNAMIC if there is no .dynamic
section.  In fact, it should work even if you do not
have any executable file at all, as it directly reads
the program headers from the target.

Is there some reason why this doesn't work for you?

Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com


  reply	other threads:[~2008-10-17 15:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-16 20:57 Aleksandar Ristovski
2008-10-17 15:22 ` Ulrich Weigand [this message]
2008-10-17 15:31   ` Aleksandar Ristovski

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=200810171520.m9HFKcns029400@d12av02.megacenter.de.ibm.com \
    --to=uweigand@de.ibm.com \
    --cc=aristovski@qnx.com \
    --cc=gdb@sources.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