From: Daniel Jacobowitz <drow@mvista.com>
To: Michal Ludvig <mludvig@suse.cz>
Cc: GDB Patches <gdb-patches@sources.redhat.com>
Subject: Re: [RFA] Dwarf2CFI fix
Date: Wed, 26 Feb 2003 17:26:00 -0000 [thread overview]
Message-ID: <20030226172553.GA14094@nevyn.them.org> (raw)
In-Reply-To: <3E5CF5F5.10300@suse.cz>
On Wed, Feb 26, 2003 at 06:14:29PM +0100, Michal Ludvig wrote:
> Hi all,
> my code in dwarf2cfi.c assumed that CIE and FDE entries in .eh_frame are
> always in the chain CIE, FDE, FDE, ..., CIE, FDE, ...
> where every FDE refers to the precedent CIE. Unfortunately this is not
> alway the case. Linker (?) sometimes optimizes things in a way that the
> assumption isn't true anymore. This patch addresses the problem.
>
> OK to commit? Head and 5.3?
> 2003-02-26 Michal Ludvig <mludvig@suse.cz>
>
> * dwarf2cfi.c (parse_frame_info): It's not true that FDEs
> always refer to the last CIE. We must deal with such a
> situation.
> * dwarf2cfi.h (
Either you're missing a bit of a patch or you're missing a bit of a
changelog. And there's no changelog entry for struct eh_frame either.
> diff -upr gdb-upto-08/dwarf2cfi.c gdb/dwarf2cfi.c
> --- gdb-upto-08/dwarf2cfi.c 2003-02-26 10:20:02.000000000 +0100
> +++ gdb/dwarf2cfi.c 2003-02-26 17:17:30.000000000 +0100
> @@ -50,6 +50,10 @@ struct cie_unit
> char *data;
> unsigned int data_length;
>
> + /* This field is 1 for CIE from .eh_frame
> + and 0 for one from .debug_frame. */
Formatting: don't wrap that early, and two spaces after a period.
The patch itself looks OK.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-02-26 17:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-26 17:14 Michal Ludvig
2003-02-26 17:26 ` Daniel Jacobowitz [this message]
2003-02-26 22:07 ` Michal Ludvig
2003-02-26 22:15 ` Daniel Jacobowitz
2003-02-27 8:29 ` Michal Ludvig
2003-02-27 17:09 ` Elena Zannoni
2003-02-27 17:18 ` Andreas Jaeger
2003-02-28 7:14 ` Michal Ludvig
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=20030226172553.GA14094@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=mludvig@suse.cz \
/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