Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Doug Evans <xdje42@gmail.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] dwarf.exp: All numeric attributes require a form
Date: Sun, 11 Jan 2015 23:48:00 -0000	[thread overview]
Message-ID: <CAP9bCMReEwvtqEnqWwd_DPhPu-FA=vrSyAt1agQuJyPnJN8P=Q@mail.gmail.com> (raw)
In-Reply-To: <CAP9bCMSCfKUGi0KJtStRFhyJurhv-JpKtjt3VC=fJgMDwMUhyA@mail.gmail.com>

On Sat, Jan 3, 2015 at 11:25 AM, Doug Evans <xdje42@gmail.com> wrote:
> On Sat, Jan 3, 2015 at 11:21 AM, Doug Evans <xdje42@gmail.com> wrote:
>> Hi.
>>
>> As a followup to this patch:
>> https://sourceware.org/ml/gdb-patches/2015-01/msg00020.html
>>
>> this patch flags as an error any numeric attribute that doesn't
>> specify a form.  And lo and behold I found more bugs. :-)
>>
>> Regression tested on amd64-linux.
>>
>> 2015-01-03  Doug Evans  <xdje42@gmail.com>
>>
>>         * lib/dwarf.exp (Dwarf): Flag an error if a numeric attribute value
>>         is given without an explicit form.
>>         * gdb.dwarf2/arr-subrange.exp: Specify forms for all numeric
>>         attributes.
>>         * gdb.dwarf/corrupt.exp: Ditto.
>>         * gdb.dwarf2/enum-type.exp: Ditto.
>>         * gdb.trace/entry-values.exp: Ditto.
>>         * gdb.trace/unavailable-dwarf-piece.exp: Ditto.
>
> btw,
> I did think of using a more complete test than just "string is integer".
> I'm happy with whatever y'all decide.
>
> I decided against trying to guess the form for numeric attributes,
> there's just too many to choose from.

fyi, I committed this.


      reply	other threads:[~2015-01-11 23:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-03 19:22 Doug Evans
2015-01-03 19:25 ` Doug Evans
2015-01-11 23:48   ` Doug Evans [this message]

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='CAP9bCMReEwvtqEnqWwd_DPhPu-FA=vrSyAt1agQuJyPnJN8P=Q@mail.gmail.com' \
    --to=xdje42@gmail.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