Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kai Tietz <Kai.Tietz@onevision.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Reading coff-pe-read files
Date: Thu, 08 Jan 2009 13:37:00 -0000	[thread overview]
Message-ID: <OF15D970B4.0B88A96E-ONC1257538.004ACDFB-C1257538.004ADC02@onevision.de> (raw)
In-Reply-To: <20090108130904.GD20220@adacore.com>

Joel Brobecker <brobecker@adacore.com> wrote on 08.01.2009 14:09:04:

> > > > > 2009-01-08  Kai Tietz  <kai.tietz@onevision.com>
> > > > > 
> > > > >         * coff-pe-read.c (read_pe_exported_syms): Enable read of 
PE+ 
> > > > > export directory.
> > 
> > Approved.
> 
> Actually, the compiler just spotted a couple of syntax errors.
> GASP! We should have both been more careful.
> Can you please fix them before checking in?
> 
> > -  if ((strcmp (target, "pe-i386") != 0) && (strcmp (target, "pei-
> i386") != 0))
> > +  is_pe64 = ((strcmp (target, "pe-x86-64") == 0)
> > +         || ((strcmp (target, "pei-x86-64") == 0));
>                ^^ One '(' too many here.
> 
> Also, I can never determine in diffs whether the weird formatting
> is because of tabs or because it is wrong.  But in this case,
> the "||" is put at the wrong location. I know it looks nicer if
> the two strcmp expressions are aligned, but any formatter will
> destroy that, and we do use GNU indent once in a while.  So let's
> be consistent and format the above as follow:
> 
> > +  is_pe64 = ((strcmp (target, "pe-x86-64") == 0)
> > +             || ((strcmp (target, "pei-x86-64") == 0));
> 
> Same for is_pe32.
> 
> > +  if (is_pe64)
> > +    num_entries = pe_get32 (dll, opthdr_ofs + 108;
>                                                     ^^
>                                           missing ')' here.
> 
> Thanks,
> -- 
> Joel
> 

I corrected it in my patch.

Sorry,
Kai

|  (\_/)  This is Bunny. Copy and paste Bunny
| (='.'=) into your signature to help him gain
| (")_(") world domination.


  reply	other threads:[~2009-01-08 13:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-07 13:51 Kai Tietz
2009-01-08  9:53 ` Joel Brobecker
2009-01-08 10:23   ` Kai Tietz
2009-01-08 11:10     ` Joel Brobecker
2009-01-08 12:53       ` Kai Tietz
2009-01-08 12:58         ` Joel Brobecker
2009-01-08 13:09           ` Joel Brobecker
2009-01-08 13:37             ` Kai Tietz [this message]
2009-01-08 20:07           ` Christopher Faylor
2009-01-08 20:55             ` Kai Tietz
2009-01-09  8:58               ` Pedro Alves
2009-01-09  9:33                 ` Kai Tietz
2009-01-08 10:36   ` Pierre Muller
  -- strict thread matches above, loose matches on Subject: below --
2009-01-07 12:27 [RFA/commit] arch-utils.c: Use host_address_to_string when printing function addresses Joel Brobecker
2009-01-07 13:15 ` [patch] Reading coff-pe-read files Kai Tietz
2009-01-07 13:54   ` Pierre Muller

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=OF15D970B4.0B88A96E-ONC1257538.004ACDFB-C1257538.004ADC02@onevision.de \
    --to=kai.tietz@onevision.com \
    --cc=brobecker@adacore.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