Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sourceware.org
Subject: [patch] Fix false warning: section .dynbss not found in ...
Date: Sun, 14 Mar 2010 21:38:00 -0000	[thread overview]
Message-ID: <20100314213746.GA32276@host0.dyn.jankratochvil.net> (raw)

Hi,

this is a follow-up on:
	http://sourceware.org/ml/gdb-patches/2010-02/msg00345.html
	http://sourceware.org/ml/gdb-patches/2010-02/msg00345.html

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

Checked the prelink source (again) and I see no more of them there now.

No regressions on {x86_64,x86_64-m32,i686}-fedora12-linux-gnu.


Thanks,
Jan


2010-03-14  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* symfile.c (addr_info_make_relative): Ignore also missing ".dynbss"
	and ".sdynbss".  Simplify the comment.

--- a/gdb/symfile.c
+++ b/gdb/symfile.c
@@ -577,15 +577,16 @@ addr_info_make_relative (struct section_addr_info *addrs, bfd *abfd)
 	     unexpected and we want to issue a warning.
 
 	     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.  */
 
 	  if (!(strcmp (sect_name, ".gnu.liblist") == 0
-		|| strcmp (sect_name, ".gnu.conflict") == 0))
+		|| strcmp (sect_name, ".gnu.conflict") == 0
+		|| strcmp (sect_name, ".dynbss") == 0
+		|| strcmp (sect_name, ".sdynbss") == 0))
 	    warning (_("section %s not found in %s"), sect_name,
 		     bfd_get_filename (abfd));
 


             reply	other threads:[~2010-03-14 21:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-14 21:38 Jan Kratochvil [this message]
2010-03-15  0:45 ` Joel Brobecker
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=20100314213746.GA32276@host0.dyn.jankratochvil.net \
    --to=jan.kratochvil@redhat.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