From: Joel Brobecker <brobecker@adacore.com>
To: Fawzi Mohamed <fawzi.mohamed@nokia.com>
Cc: gdb-patches@sourceware.org,
ext Tristan Gingold <gingold@adacore.com>,
Andr? P?nitz <andre.poenitz@nokia.com>
Subject: Re: [PATCH,gdb, Update1]: ensures that cie ptr of an fda is a cie
Date: Tue, 05 Jul 2011 15:17:00 -0000 [thread overview]
Message-ID: <20110705151427.GW2407@adacore.com> (raw)
In-Reply-To: <29C73230-F22F-4551-B99F-B21E6B61CCAF@nokia.com>
> 2011-07-04 Fawzi Mohamed <fawzi.mohamed@nokia.com>
>
> * dwarf2-frame.c (decode_frame_entry, decode_frame_entry_1): ensure
> that CIE pointer of an FDE really points to a CIE
Just a few more nits... (a lot of rules, I know, but we try to have
a consistent development style).
First, in the ChangeLog above: 2 spaces between the date and your
name, and before your email address. Also, sentences always start
with a capital letter, and end with a period. Thus
2011-07-04 Fawzi Mohamed <fawzi.mohamed@nokia.com>
* dwarf2-frame.c (decode_frame_entry, decode_frame_entry_1): Ensure
that CIE pointer of an FDE really points to a CIE .
> +/* defines the type of eh_frames that are expected to be decoded: CIE, FDE
> + or any of them */
> +enum eh_frame_type
Empty line between documentation comment and start of definition...
> +{
> + eh_cie_type_id = 1<<0,
> + eh_fde_type_id = 1<<1,
> + eh_cie_or_fde_type_id = eh_cie_type_id + eh_fde_type_id
> +};
Spaces around binary operators => `1 << 0'.
> -/* Decode the next CIE or FDE. Return NULL if invalid input, otherwise
> - the next byte to be processed. */
> +/* Decode the next CIE or FDE, entry type specifies the expected type.
> + Return NULL if invalid input, otherwise the next byte to be processed. */
> static gdb_byte *
Same here...
> + /* checks that we expected a CIE */
> + gdb_assert ((entry_type & eh_cie_type_id) != 0);
Same here as well. But I think you meant something like `We expect
a CIE.'.
--
Joel
next prev parent reply other threads:[~2011-07-05 15:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-04 18:19 [PATCH,gdb]: " Fawzi Mohamed
2011-07-04 18:52 ` Joel Brobecker
2011-07-05 10:44 ` [PATCH,gdb, Update1]: " Fawzi Mohamed
2011-07-05 15:17 ` Joel Brobecker [this message]
2011-07-05 16:57 ` [PATCH,gdb, Update2]: " Fawzi Mohamed
2011-07-05 16:26 ` [PATCH,gdb]: " Tom Tromey
2011-07-06 14:45 ` [PATCH,gdb,Update3]: " Fawzi Mohamed
2011-07-06 18:16 ` Jan Kratochvil
2011-07-07 17:17 ` [PATCH,gdb,Update4]: " Fawzi Mohamed
2011-07-07 23:37 ` Tom Tromey
2011-07-11 17:19 ` [PATCH,gdb,Update6]: " Fawzi Mohamed
2011-07-11 21:52 ` Tom Tromey
2011-07-12 11:15 ` [PATCH,gdb,Update7]: " Fawzi Mohamed
2011-07-12 20:01 ` Tom Tromey
2011-07-15 15:34 ` FYI " Fawzi Mohamed
2011-07-07 18:48 ` [PATCH,gdb,Update5]: " Fawzi Mohamed
2011-07-07 19:38 ` Tom Tromey
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=20110705151427.GW2407@adacore.com \
--to=brobecker@adacore.com \
--cc=andre.poenitz@nokia.com \
--cc=fawzi.mohamed@nokia.com \
--cc=gdb-patches@sourceware.org \
--cc=gingold@adacore.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