Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jonathan Larmour <jifl@eCosCentric.com>
To: gdb-patches@sourceware.org
Subject: Re: Avoid potential crashes with --gc-sections and low addresses
Date: Fri, 27 Jun 2008 18:31:00 -0000	[thread overview]
Message-ID: <48652F49.2070506@eCosCentric.com> (raw)
In-Reply-To: <20080627164106.GB4724@caradoc.them.org>

Daniel Jacobowitz wrote:
> On Fri, Jun 27, 2008 at 04:37:50PM +0100, Jonathan Larmour wrote:
>> --- gdb/dwarf2-frame.c~	2008-05-04 00:24:17.000000000 +0100
>> +++ gdb/dwarf2-frame.c	2008-06-20 17:06:04.000000000 +0100
>> @@ -1795,7 +1795,8 @@ decode_frame_entry_1 (struct comp_unit *
>>  
>>        fde->eh_frame_p = eh_frame_p;
>>  
>> -      add_fde (unit, fde);
>> +      if (fde->initial_location)
>> +          add_fde (unit, fde);
>>      }
>>  
>>    return end;
> 
> This won't work if there is code actually at zero.  Take a look at the
> .debug_info reader to see how we handled this case for symbolic debug info.

I've had a look, and got lost in a twisty maze of passages. The learning
curve for that stuff is probably steeper than I can manage at the moment.
If you don't mind, in that case I'll submit it to GNATS so it isn't lost.

Jifl
-- 
eCosCentric Limited      http://www.eCosCentric.com/     The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK.       Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
------["Si fractum non sit, noli id reficere"]------       Opinions==mine


  reply	other threads:[~2008-06-27 18:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-27 15:56 Jonathan Larmour
2008-06-27 16:01 ` Jonathan Larmour
2008-06-27 17:14   ` Daniel Jacobowitz
2008-06-27 18:31     ` Jonathan Larmour [this message]
2008-06-27 19:13       ` Daniel Jacobowitz

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=48652F49.2070506@eCosCentric.com \
    --to=jifl@ecoscentric.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