From: Alan Modra <amodra@bigpond.net.au>
To: Richard Henderson <rth@twiddle.net>
Cc: binutils@gcc.gnu.org
Subject: Re: [rfc] eh-frame clobbers memory
Date: Sun, 22 May 2005 17:04:00 -0000 [thread overview]
Message-ID: <20050522134215.GP27573@bubble.grove.modra.org> (raw)
In-Reply-To: <20050522101414.GA18027@twiddle.net>
On Sun, May 22, 2005 at 03:14:14AM -0700, Richard Henderson wrote:
> * elf-eh-frame.c (_bfd_elf_write_section_eh_frame): Reallocate
> contents if the section size grew.
elf_link_input_bfd will normally be using finfo.contents to buffer
eh_frame sections, so you definitely don't want to do this.
I suppose alpha must be stashing .eh_frame contents away in
elf_section_data this_hdr.contents, during elf64_alpha_relax_section.
Avoid that for .eh_frame and everything should work.
--
Alan Modra
IBM OzLabs - Linux Technology Centre
next prev parent reply other threads:[~2005-05-22 13:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-22 10:19 Richard Henderson
2005-05-22 13:42 ` John Levon
2005-05-22 17:04 ` Alan Modra [this message]
2005-05-22 22:21 ` Richard Henderson
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=20050522134215.GP27573@bubble.grove.modra.org \
--to=amodra@bigpond.net.au \
--cc=binutils@gcc.gnu.org \
--cc=rth@twiddle.net \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).