Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: Mark Kettenis <kettenis@chello.nl>
Cc: Richard Henderson <rth@twiddle.net>,
	ezannoni@redhat.com, gdb-patches@gcc.gnu.org
Subject: Re: [RFA] Don't SEGV on invalid dwarf2 frame info
Date: Thu, 10 Jul 2003 21:21:00 -0000	[thread overview]
Message-ID: <16141.55923.596252.107277@localhost.redhat.com> (raw)
In-Reply-To: <86wueqp075.fsf@elgar.kettenis.dyndns.org>

Mark Kettenis writes:
 > Richard Henderson <rth@twiddle.net> writes:
 > 
 > > Elena, this is the patch I was thinking about.
 > > 
 > > For the audience, there is at least one bug in current cvs ld's .eh_frame
 > > optimization code that results in padding being added between sections.
 > > But we saw similar problems when we added support for .eh_frame generation
 > > within the assembler (and didn't .align sections), so the discussion in 
 > > the patch is a bit more broad than that.
 > > 
 > > Does this seem reasonable?
 > 
 > It does to me.  It's unfortunately that this is necessary, but it
 > makes things more robust, so please check this in.
 > 
 > Mark

As is, the patch doesn't compile. I'll have updated one in a minute. I
also think that there should be a check after reading the
initial_length, that such length is within the section. In my case,
that's where gdb encounters the first bogus value.

elena


  reply	other threads:[~2003-07-10 21:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-10  1:03 Richard Henderson
2003-07-10 20:59 ` Mark Kettenis
2003-07-10 21:21   ` Elena Zannoni [this message]
2003-07-10 22:44     ` Richard Henderson
2003-07-10 22:59       ` Elena Zannoni
2003-07-10 23:48         ` Richard Henderson
2003-07-10 22:19   ` Elena Zannoni
2003-07-10 22:48     ` Richard Henderson
2003-07-10 22:58       ` Elena Zannoni
2003-07-11 16:24         ` Richard Henderson
2003-07-11 16:40           ` Elena Zannoni

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=16141.55923.596252.107277@localhost.redhat.com \
    --to=ezannoni@redhat.com \
    --cc=gdb-patches@gcc.gnu.org \
    --cc=kettenis@chello.nl \
    --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