From: Joel Brobecker <brobecker@adacore.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Fix false warning: section .dynbss not found in ...
Date: Mon, 15 Mar 2010 00:45:00 -0000 [thread overview]
Message-ID: <20100315004502.GE3045@adacore.com> (raw)
In-Reply-To: <20100314213746.GA32276@host0.dyn.jankratochvil.net>
> found two new sections by prelink:
> Reading symbols from /usr/bin/gdb...Reading symbols from /usr/lib/debug/usr/bin/gdb.debug...
> warning: section .dynbss not found in /usr/lib/debug/usr/bin/gdb.debug
:-) I was afraid that we'd find some of other sections that
needed to be excluded... :-/
> 2010-03-14 Jan Kratochvil <jan.kratochvil@redhat.com>
>
> * symfile.c (addr_info_make_relative): Ignore also missing ".dynbss"
> and ".sdynbss". Simplify the comment.
OK, at least for now, but just a nit:
> However, the ELF prelinker does create a couple of sections
> - (".gnu.liblist" and ".gnu.conflict") which are marked in the main
> - executable as loadable (they are loaded in memory from the
> - DYNAMIC segment) and yet are not present in separate debug info
> - files. This is fine, and should not cause a warning. Shared
> - libraries contain just the section ".gnu.liblist" but it is not
> - marked as loadable there. */
> + which are marked in the main executable as loadable (they are
> + loaded in memory from the DYNAMIC segment) and yet are not present
> + in separate debug info files. This is fine, and should not cause
> + a warning. Shared libraries contain just the section
> + ".gnu.liblist" but it is not marked as loadable there. */
The comment should say "a few sections" as opposed to "a couple" (a
couple is two, or three at most), and it should say that there is no
other way to identify these section except by name.
Pre-approved with that comment update.
--
Joel
next prev parent reply other threads:[~2010-03-15 0:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-14 21:38 Jan Kratochvil
2010-03-15 0:45 ` Joel Brobecker [this message]
2010-03-15 9:36 ` Jan Kratochvil
2010-03-15 16:43 ` Joel Brobecker
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=20100315004502.GE3045@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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