From: Michal Ludvig <mludvig@suse.cz>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: GDB Patches <gdb-patches@sources.redhat.com>
Subject: Re: [RFA] Dwarf2CFI fix
Date: Wed, 26 Feb 2003 22:07:00 -0000 [thread overview]
Message-ID: <3E5D3AAA.4070106@suse.cz> (raw)
In-Reply-To: <20030226172553.GA14094@nevyn.them.org>
Daniel Jacobowitz wrote:
> 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.
Oops, sorry. The changelog wasn't yet saved while I was sending the mail...
Here it goes:
2003-02-26 Michal Ludvig <mludvig@suse.cz>
* dwarf2cfi.c (struct cie_unit): Added eh_frame field.
(parse_frame_info): It's not true that FDEs always refer to
the last CIE. We must deal with such a situation.
>>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.
OK, I'll reindent it with gdb_indent.sh before committing.
> The patch itself looks OK.
Is this an approval? :-)
Michal Ludvig
--
* SuSE CR, s.r.o * mludvig@suse.cz
* (+420) 296.545.373 * http://www.suse.cz
next prev parent reply other threads:[~2003-02-26 22:07 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
2003-02-26 22:07 ` Michal Ludvig [this message]
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=3E5D3AAA.4070106@suse.cz \
--to=mludvig@suse.cz \
--cc=drow@mvista.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