Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tromey@redhat.com>, Doug Evans <dje@google.com>
Subject: Re: [patch] Fix ELF stale reference
Date: Thu, 14 Oct 2010 16:07:00 -0000	[thread overview]
Message-ID: <20101014160653.GA24333@host1.dyn.jankratochvil.net> (raw)
In-Reply-To: <20100909145615.GA5771@host1.dyn.jankratochvil.net>

Hi,

I was debugging https://bugzilla.redhat.com/show_bug.cgi?id=642879 and got to
this fix from a different side.  It is in fact a very common GDB crash - due
to CTRL-C hit (to get GDB prompt) in the moment an ELF file is being read in.

Original thread: http://sourceware.org/ml/gdb-patches/2010-09/msg00192.html


On Thu, 09 Sep 2010 16:56:15 +0200, Jan Kratochvil wrote:
> OTOH this patch is not completely clean, it can needlessly allocate
> bfd-associated memory and the right fix would probably span into bfd/ IMO.

While the memory could use for example register_objfile_data_with_cleanup
instead of bfd_alloc so that if errors/CTRL-Cs happen the dynamic symbol table
pointers memory is not allocated twice.   Still I would not find it correct as
such memory would be objfile-bound instead of abfd-bound - while being
referenced by abfd.

OK to check-in?  Or some bfd/ API improvement should be made?


Thanks,
Jan


gdb/
2010-09-09  Jan Kratochvil  <jan.kratochvil@redhat.com>

	Fix stale memory references.
	* elfread.c: Include libbfd.h.
	(elf_symfile_read): Replace xmalloc by bfd_alloc, drop xfree, new
	comment.

--- a/gdb/elfread.c
+++ b/gdb/elfread.c
@@ -37,6 +37,7 @@
 #include "complaints.h"
 #include "demangle.h"
 #include "psympriv.h"
+#include "libbfd.h"
 
 extern void _initialize_elfread (void);
 
@@ -792,8 +793,14 @@ elf_symfile_read (struct objfile *objfile, int symfile_flags)
 
   if (storage_needed > 0)
     {
-      dyn_symbol_table = (asymbol **) xmalloc (storage_needed);
-      make_cleanup (xfree, dyn_symbol_table);
+      /* Memory gets permanently referenced from ABFD after
+	 bfd_get_synthetic_symtab so it must not get freed before ABFD gets.
+	 It happens only in the case when elf_slurp_reloc_table sees
+	 asection->relocation NULL.  Determining which section is asection is
+	 done by _bfd_elf_get_synthetic_symtab which is all a bfd
+	 implementation detail, though.  */
+
+      dyn_symbol_table = bfd_alloc (abfd, storage_needed);
       dynsymcount = bfd_canonicalize_dynamic_symtab (objfile->obfd,
 						     dyn_symbol_table);
 


  reply	other threads:[~2010-10-14 16:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-08 19:40 [patch] .gdb_index: Do not crash on NOBITS Jan Kratochvil
2010-09-08 23:19 ` Tom Tromey
2010-09-08 23:36   ` Jan Kratochvil
2010-09-09 14:05   ` [patch] Fix ELF stale reference [Re: [patch] .gdb_index: Do not crash on NOBITS] Jan Kratochvil
2010-09-09 16:01     ` Doug Evans
2010-09-09 16:11       ` Jan Kratochvil
2010-10-14 16:07         ` Jan Kratochvil [this message]
2010-10-14 17:46           ` [patch] Fix ELF stale reference Tom Tromey
2010-11-19 22:49             ` Jan Kratochvil

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=20101014160653.GA24333@host1.dyn.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@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