From: Tom Tromey <tromey@redhat.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: FYI: fix error in py-type.c
Date: Thu, 07 Feb 2013 20:58:00 -0000 [thread overview]
Message-ID: <87k3qjvo31.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CADPb22S3MdZUr+JNQajK38np7tZnHfY1_-_qhjp+0COSv0Sr0Q@mail.gmail.com> (Doug Evans's message of "Thu, 7 Feb 2013 11:22:30 -0800")
>>>>> "Doug" == Doug Evans <dje@google.com> writes:
Doug> I think the bar for contrib is in general lower.
Doug> I think you should feel free to add the FIXMEs you deem appropriate
Doug> and check it in.
Doug> [... and maybe leverage the net to fix them for you :-)]
I'll send the series in a minute.
What I did is add some options to the summarizer script.
The default is to disable reporting for the checks that are generally
not useful. I checked the indirect function call errors and for the
most part they aren't important.
After the series I still get the appended.
This is a bug, but pretty obscure.
Tom
../../archer/gdb/python/py-cmd.c:404: error: function cmdpy_init is marked nothrow but can throw
../../archer/gdb/python/py-cmd.c:451: info: via call to gdbpy_parse_command_name
../../archer/gdb/python/py-cmd.c:359: info: via call to lookup_cmd_1
../../archer/gdb/cli/cli-decode.c:1381: info: via call to deprecated_cmd_warning
../../archer/gdb/cli/cli-decode.c:1587: info: via call to printf_filtered
../../archer/gdb/utils.c:2437: info: via call to vfprintf_filtered
../../archer/gdb/utils.c:2348: info: via call to vfprintf_maybe_filtered
../../archer/gdb/utils.c:2340: info: via call to fputs_maybe_filtered
../../archer/gdb/utils.c:2112: info: via call to prompt_for_continue
../../archer/gdb/utils.c:1902: info: via call to quit
../../archer/gdb/utils.c:1142: info: via call to fatal
../../archer/gdb/utils.c:740: info: via call to throw_vfatal
../../archer/gdb/python/py-param.c:655: error: function parmpy_init is marked nothrow but can throw
../../archer/gdb/python/py-param.c:709: info: via call to gdbpy_parse_command_name
../../archer/gdb/python/py-cmd.c:359: info: via call to lookup_cmd_1
../../archer/gdb/cli/cli-decode.c:1381: info: via call to deprecated_cmd_warning
../../archer/gdb/cli/cli-decode.c:1587: info: via call to printf_filtered
../../archer/gdb/utils.c:2437: info: via call to vfprintf_filtered
../../archer/gdb/utils.c:2348: info: via call to vfprintf_maybe_filtered
../../archer/gdb/utils.c:2340: info: via call to fputs_maybe_filtered
../../archer/gdb/utils.c:2112: info: via call to prompt_for_continue
../../archer/gdb/utils.c:1902: info: via call to quit
../../archer/gdb/utils.c:1142: info: via call to fatal
../../archer/gdb/utils.c:740: info: via call to throw_vfatal
prev parent reply other threads:[~2013-02-07 20:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 16:54 Tom Tromey
2013-02-06 21:51 ` Doug Evans
2013-02-06 22:00 ` Tom Tromey
2013-02-07 19:22 ` Doug Evans
2013-02-07 20:58 ` Tom Tromey [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=87k3qjvo31.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=dje@google.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