From: Andrew Cagney <ac131313@redhat.com>
To: Andreas Schwab <schwab@suse.de>
Cc: gdb-patches@sources.redhat.com, Nick Clifton <nickc@redhat.com>,
Alan Modra <amodra@bigpond.net.au>
Subject: Re: Fix hash table mixup in bfd_simple_get_relocated_section_content
Date: Wed, 17 Sep 2003 20:42:00 -0000 [thread overview]
Message-ID: <3F68C71D.8010009@redhat.com> (raw)
In-Reply-To: <jek787yzhr.fsf@sykes.suse.de>
> Andrew Cagney <ac131313@redhat.com> writes:
>
>
>>> Daniel Jacobowitz <drow@mvista.com> writes:
>>>
>
>>>> On Wed, Sep 17, 2003 at 06:04:05PM +0200, Andreas Schwab wrote:
>
>>>
>
>>>>> bfd_simple_get_relocated_section_content uses the generic linker
>>>>> interface, so it should also use the generic_link_hash_table.
>
>>>
>
>>>>
>>>> Hmm, this seems right to me.
>
>>> Posted now to binutils@ where it belongs, but I think this should be
>>> added to gdb-6.0 because it also affects add-symbol.
>
>>
>> Grrrr :-)
>>
>> What's the damage without it?
>
>
> You can get random crashes in generic_link_add_symbol_list because
> _bfd_generic_link_add_one_symbol hands out a bfd_link_hash_entry, but a
> generic_link_hash_entry is expected, and h->sym remains uninitialized.
> The specific case where it happend was gdb debugging a user mode linux
> process, and applying add-symbol to a kernel module.
If you can extract a "safe for GDB's branch" from Nick or Alan then it's
approved.
Andrew
next prev parent reply other threads:[~2003-09-17 20:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-17 16:04 Andreas Schwab
2003-09-17 16:09 ` Daniel Jacobowitz
2003-09-17 16:46 ` Andreas Schwab
2003-09-17 18:26 ` Andrew Cagney
2003-09-17 19:41 ` Andreas Schwab
2003-09-17 20:42 ` Andrew Cagney [this message]
2003-09-18 1:57 ` Alan Modra
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=3F68C71D.8010009@redhat.com \
--to=ac131313@redhat.com \
--cc=amodra@bigpond.net.au \
--cc=gdb-patches@sources.redhat.com \
--cc=nickc@redhat.com \
--cc=schwab@suse.de \
/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