From: Michael Snyder <msnyder@vmware.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: New ARI warning Fri Jan 7 01:54:25 UTC 2011
Date: Fri, 07 Jan 2011 02:18:00 -0000 [thread overview]
Message-ID: <4D2677E5.5020704@vmware.com> (raw)
In-Reply-To: <20110107015425.GA12157@sourceware.org>
GDB Administrator wrote:
> 622a623,624
>> gdb/mi/mi-cmd-disas.c:131: gettext: _ markup: All messages should be marked up with _.
> gdb/mi/mi-cmd-disas.c:131: error ("mi_cmd_disassemble: Usage: ( [-f filename -l linenum [-n "
>> gdb/mi/mi-cmd-disas.c:135: gettext: _ markup: All messages should be marked up with _.
> gdb/mi/mi-cmd-disas.c:135: error ("mi_cmd_disassemble: Usage: [-f filename -l "
> 1072d1073
> < gdb/solib-irix.c:575: gettext: _ markup: All messages should be marked up with _.
> gdb/solib-irix.c:575: warning ("current_sos: truncating name of "
> 1249d1249
> < gdb/tui/tui-layout.c:487: code: OP eol: Do not use &&, or || at the end of a line
> gdb/tui/tui-layout.c:487: if (TUI_DATA_WIN->detail.data_display_info.regs_display_type !=
> 1267a1268
>> gdb/tui/tui-winsource.c:346: code: if assignment: An IF statement's expression contains an assignment (the GNU coding standard discourages this)
> gdb/tui/tui-winsource.c:346: if ((offset = win_info->detail.source_info.horizontal_offset - num_to_scroll) < 0)
> 1321d1321
> < gdb/varobj.c:2063: gettext: _ markup: All messages should be marked up with _.
> gdb/varobj.c:2063: warning ("Assertion failed: Could not find "
Hmmm, these are all files that I touched, but the issues are all
pre-existing. What's going on? Why the new warnings?
next prev parent reply other threads:[~2011-01-07 2:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-07 1:54 GDB Administrator
2011-01-07 2:18 ` Michael Snyder [this message]
2011-01-07 4:14 ` Joel Brobecker
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=4D2677E5.5020704@vmware.com \
--to=msnyder@vmware.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