From: Andreas Schwab <schwab@suse.de>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Fix hash table mixup in bfd_simple_get_relocated_section_content
Date: Wed, 17 Sep 2003 19:41:00 -0000 [thread overview]
Message-ID: <jek787yzhr.fsf@sykes.suse.de> (raw)
In-Reply-To: <3F68A762.50601@redhat.com> (Andrew Cagney's message of "Wed, 17 Sep 2003 14:26:42 -0400")
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.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2003-09-17 19:41 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 [this message]
2003-09-17 20:42 ` Andrew Cagney
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=jek787yzhr.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=ac131313@redhat.com \
--cc=gdb-patches@sources.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