From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Aleksandar Ristovski <aristovski@qnx.com>
Subject: Re: [patch] solib-svr4.c - allow reading linkmap info from core without executable
Date: Thu, 18 Jun 2009 23:03:00 -0000 [thread overview]
Message-ID: <200906190004.23937.pedro@codesourcery.com> (raw)
In-Reply-To: <4A310906.4030603@qnx.com>
On Thursday 11 June 2009 14:39:18, Aleksandar Ristovski wrote:
> Pedro Alves wrote:
> >> if (info->debug_base == 0 && svr4_have_link_map_offsets ())
> >> {
> >> - if (exec_bfd != NULL
> >> + if ((exec_bfd != NULL
> >> && bfd_get_flavour (exec_bfd) == bfd_target_elf_flavour)
> >> + || (core_bfd != NULL
> >> + && bfd_get_flavour (core_bfd) == bfd_target_elf_flavour))
> >> info->debug_base = elf_locate_base ();
> >> }
> >
> > Are there live debugging cases (archs?, PIE?) (e.g., "target remote"
> > without specifying an executable) where letting elf_locate_base
> > try to read the debug base from the target's auxv (scan_dyntag_auxv)
> > will work? It would mean that removing the exec_bfd checks instead
> > of adding core_bfd checks, would still improve your case, while
> > letting other cases benefit as well.
> >
>
> Yes, in theory it should work as long as target_ops in
> question know how to read auxv (that is, as long as
> to_xfer_partial(ops, TARGET_OBJECT_AUXV,...) knows how to do
> it.)
>
> I had internally made this change:
>
> {
> - if (exec_bfd != NULL
> + if ((exec_bfd != NULL
> && bfd_get_flavour (exec_bfd) ==
> bfd_target_elf_flavour)
> + || exec_bfd == NULL)
> debug_base = elf_locate_base ();
> }
> return (debug_base);
>
>
> But wanted to be more conservative for FSF, since I do not
> quite understand under which circumstances could we end up
> in solib-svr4, and not have "bfd_target_elf_flavour".
I was thinking on pushing the elf check a bit down instead,
like the below. However, having now tested this, I see that
this doesn't work in most of the cores I have here (x86_64-linux).
In most cases I see, the segment that would contain the program
headers, as indicated by auxv info, isn't included in the
core...
(objdump -h)
Idx Name Size VMA LMA File off Algn
:
6 load1 00000000 0000000000400000 0000000000000000 000008f8 2**0
ALLOC, READONLY, CODE
:
--
Pedro Alves
---
gdb/solib-svr4.c | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
Index: src/gdb/solib-svr4.c
===================================================================
--- src.orig/gdb/solib-svr4.c 2009-06-18 20:55:50.000000000 +0100
+++ src/gdb/solib-svr4.c 2009-06-18 22:25:11.000000000 +0100
@@ -266,7 +266,7 @@ IGNORE_FIRST_LINK_MAP_ENTRY (struct so_l
/* Assume that everything is a library if the dynamic loader was loaded
late by a static executable. */
- if (bfd_get_section_by_name (exec_bfd, ".dynamic") == NULL)
+ if (exec_bfd && bfd_get_section_by_name (exec_bfd, ".dynamic") == NULL)
return 0;
return extract_typed_address (so->lm_info->lm + lmo->l_prev_offset,
@@ -600,9 +600,13 @@ scan_dyntag (int dyntag, bfd *abfd, CORE
if (abfd == NULL)
return 0;
+
+ if (bfd_get_flavour (abfd) != bfd_target_elf_flavour)
+ return 0;
+
arch_size = bfd_get_arch_size (abfd);
if (arch_size == -1)
- return 0;
+ return 0;
/* Find the start address of the .dynamic section. */
sect = bfd_get_section_by_name (abfd, ".dynamic");
@@ -825,11 +829,7 @@ locate_base (struct svr4_info *info)
though if we don't have some link map offsets to work with. */
if (info->debug_base == 0 && svr4_have_link_map_offsets ())
- {
- if (exec_bfd != NULL
- && bfd_get_flavour (exec_bfd) == bfd_target_elf_flavour)
- info->debug_base = elf_locate_base ();
- }
+ info->debug_base = elf_locate_base ();
return info->debug_base;
}
next prev parent reply other threads:[~2009-06-18 23:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-29 20:42 Aleksandar Ristovski
2009-06-10 22:07 ` Pedro Alves
2009-06-11 13:39 ` Aleksandar Ristovski
2009-06-18 14:04 ` Aleksandar Ristovski
2009-06-18 23:03 ` Pedro Alves [this message]
2009-06-19 14:16 ` Aleksandar Ristovski
2009-06-19 14:42 ` Mark Kettenis
2009-06-19 14:56 ` Daniel Jacobowitz
2009-06-19 15:00 ` Pedro Alves
2009-06-19 16:03 ` Aleksandar Ristovski
2009-06-20 0:17 ` 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=200906190004.23937.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=aristovski@qnx.com \
--cc=gdb-patches@sourceware.org \
/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