Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Correct `gcc -D' macros get ignored (PR 9873)
Date: Mon, 09 Mar 2009 18:41:00 -0000	[thread overview]
Message-ID: <20090309184138.GB4561@adacore.com> (raw)
In-Reply-To: <20090309005707.GB29150@host0.dyn.jankratochvil.net>

> 2009-03-09  Jan Kratochvil  <jan.kratochvil@redhat.com>
> 
>         PR gdb/9873:
>         * dwarf2read.c (dwarf_decode_macros): New variable `at_commandline'.
>         Move the variable `macinfo_type' out of the loop.  Create a new
>         processing pass before the current one to pre-create `current_file'.
>         New complaint on misplaced zero/non-zero definitions/includes.
>         Skip first DW_MACINFO_start_file with `at_commandline' set.

This is OK, with one tiny typo (and I'm probably the one responsible
for it).

> Sure I find your text better although its first line does not follow the GNU
> Coding Style directive `[...] please write complete sentences [...]'.
> Used your text.

Are you refering to the "First pass:"? I think it's OK.

> OK although it was catching both inconsistencies so it has to be written as
> 
>   if ((line == 0 && !at_commandline) || (line != 0 && at_commandline))

Right!

> +     associated to base file.
                    ^^^ "the" base file...

Cheers,
-- 
Joel


  reply	other threads:[~2009-03-09 18:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-20  0:20 Jan Kratochvil
     [not found] ` <20090228071514.GA25299@adacore.com>
     [not found]   ` <20090228100225.GA15788@host0.dyn.jankratochvil.net>
2009-03-03  0:54     ` Joel Brobecker
2009-03-09  0:57       ` Jan Kratochvil
2009-03-09 18:41         ` Joel Brobecker [this message]
2009-03-09 18:56           ` Jan Kratochvil

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=20090309184138.GB4561@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@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