From: Doug Evans <dje@google.com>
To: "Sérgio Durigan Júnior" <sergiodj@linux.vnet.ibm.com>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [RFC] Wording of "catch syscall <number>" warning
Date: Fri, 25 Sep 2009 05:35:00 -0000 [thread overview]
Message-ID: <e394668d0909242235k57c2ecd7s879718a6fcc0c734@mail.gmail.com> (raw)
In-Reply-To: <200909242338.37707.sergiodj@linux.vnet.ibm.com>
2009/9/24 Sérgio Durigan Júnior <sergiodj@linux.vnet.ibm.com>:
> On Thursday 24 September 2009, Joel Brobecker wrote:
>> warning: This debugger was compiled without XML support.
>> It will not be able to verify the validity of syscall numbers.
>
> I see your point. We already warn the user (only once) if GDB won't be able
> to display syscall names, but we don't tell anything about GDB not being able
> to verify the validity of syscall numbers. Maybe we should include this
> information in this "one-time warning", and remove the other warnings then.
"works for me", modulo I tend to gloss over the messages gdb prints at
start up. :-)
OTOH, I'm all for keeping the code simple too.
One thing I don't like about my patch is that I'd rather only print
the warning once too.
So how about for now just enhancing the warning at start up, and not
printing anything later on.
next prev parent reply other threads:[~2009-09-25 5:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-25 0:31 Doug Evans
2009-09-25 1:49 ` Joel Brobecker
2009-09-25 2:02 ` Sérgio Durigan Júnior
2009-09-25 2:20 ` Joel Brobecker
2009-09-25 2:38 ` Sérgio Durigan Júnior
2009-09-25 5:35 ` Doug Evans [this message]
2009-09-25 15:30 ` Joel Brobecker
2009-09-25 15:45 ` Tom Tromey
2009-09-25 16:07 ` Joel Brobecker
2009-09-25 16:50 ` Sérgio Durigan Júnior
2009-09-25 1:57 ` Sérgio Durigan Júnior
2009-09-25 15:45 ` Tom Tromey
2009-09-25 16:50 ` Sérgio Durigan Júnior
2009-09-25 19:39 ` Sérgio Durigan Júnior
2009-09-25 20:15 ` Doug Evans
2009-09-26 19:18 ` Sérgio Durigan Júnior
2009-09-26 23:34 ` Sérgio Durigan Júnior
2009-09-28 5:09 ` Doug Evans
2009-10-03 3:19 ` Sérgio Durigan Júnior
2009-10-31 6:02 ` Sérgio Durigan Júnior
2009-09-25 23:00 ` Sérgio Durigan Júnior
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=e394668d0909242235k57c2ecd7s879718a6fcc0c734@mail.gmail.com \
--to=dje@google.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@linux.vnet.ibm.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