From: GDB Administrator <gdbadmin@sourceware.org>
To: gdb-patches@sourceware.org
Subject: New ARI warning Thu Feb 14 01:59:49 UTC 2013 in -D 2013-02-14-gmt
Date: Thu, 14 Feb 2013 02:00:00 -0000 [thread overview]
Message-ID: <20130214015949.GA27541@sourceware.org> (raw)
1,9d0
< gdb/aarch64-linux-nat.c:146: code: long long: Do not use 'long long', instead use LONGEST
gdb/aarch64-linux-nat.c:146:typedef unsigned long long dr_changed_t;
< gdb/aarch64-linux-nat.c:338: code: %ll: Do not use printf(%ll), instead use printf(%s,phex()) to dump a 'long long' value
gdb/aarch64-linux-nat.c:338: "\tpid%d, dr_changed_bp=0x%llx, "
< gdb/aarch64-linux-nat.c:339: code: %ll: Do not use printf(%ll), instead use printf(%s,phex()) to dump a 'long long' value
gdb/aarch64-linux-nat.c:339: "dr_changed_wp=0x%llx\n",
< gdb/aarch64-linux-nat.c:364: code: %ll: Do not use printf(%ll), instead use printf(%s,phex()) to dump a 'long long' value
gdb/aarch64-linux-nat.c:364: "\tOn exit:\n\tpid%d, dr_changed_bp=0x%llx, "
< gdb/aarch64-linux-nat.c:365: code: %ll: Do not use printf(%ll), instead use printf(%s,phex()) to dump a 'long long' value
gdb/aarch64-linux-nat.c:365: "dr_changed_wp=0x%llx\n",
< gdb/aarch64-linux-nat.c:736: gettext: _ markup: All messages should be marked up with _.
gdb/aarch64-linux-nat.c:736: warning ("Unexpected number of hardware watchpoint registers reported"
< gdb/aarch64-linux-nat.c:744: gettext: _ markup: All messages should be marked up with _.
gdb/aarch64-linux-nat.c:744: warning ("Unable to determine the number of hardware watchpoints"
< gdb/aarch64-linux-nat.c:756: gettext: _ markup: All messages should be marked up with _.
gdb/aarch64-linux-nat.c:756: warning ("Unexpected number of hardware breakpoint registers reported"
< gdb/aarch64-linux-nat.c:764: gettext: _ markup: All messages should be marked up with _.
gdb/aarch64-linux-nat.c:764: warning ("Unable to determine the number of hardware breakpoints"
27a19,20
> gdb/amd64-linux-nat.c:469: comment: GNU/Linux: Do not use 'Linux', instead use 'Linux kernel' or 'GNU/Linux system'; comments should clearly differentiate between the two (this test assumes that word 'Linux' appears on the same line as the word 'GNU' or 'kernel' or a kernel version
gdb/amd64-linux-nat.c:469: this compatible with older Linux kernels too. */
> gdb/amd64-linux-nat.c:1022: comment: GNU/Linux: Do not use 'Linux', instead use 'Linux kernel' or 'GNU/Linux system'; comments should clearly differentiate between the two (this test assumes that word 'Linux' appears on the same line as the word 'GNU' or 'kernel' or a kernel version
gdb/amd64-linux-nat.c:1022:/* Get Linux/x86 target description from running target.
320a314,315
> gdb/i386-linux-nat.c:836: comment: GNU/Linux: Do not use 'Linux', instead use 'Linux kernel' or 'GNU/Linux system'; comments should clearly differentiate between the two (this test assumes that word 'Linux' appears on the same line as the word 'GNU' or 'kernel' or a kernel version
gdb/i386-linux-nat.c:836: this compatible with older Linux kernels too. */
> gdb/i386-linux-nat.c:992: comment: GNU/Linux: Do not use 'Linux', instead use 'Linux kernel' or 'GNU/Linux system'; comments should clearly differentiate between the two (this test assumes that word 'Linux' appears on the same line as the word 'GNU' or 'kernel' or a kernel version
gdb/i386-linux-nat.c:992:/* Get Linux/x86 target description from running target. */
333,334d327
< gdb/i386-nat.c:225: comment: GNU/Linux: Do not use 'Linux', instead use 'Linux kernel' or 'GNU/Linux system'; comments should clearly differentiate between the two (this test assumes that word 'Linux' appears on the same line as the word 'GNU' or 'kernel' or a kernel version
gdb/i386-nat.c:225: on fork/vfork/clone. Newer Linux kernels create such tasks with
< gdb/i386-nat.c:230: comment: GNU/Linux: Do not use 'Linux', instead use 'Linux kernel' or 'GNU/Linux system'; comments should clearly differentiate between the two (this test assumes that word 'Linux' appears on the same line as the word 'GNU' or 'kernel' or a kernel version
gdb/i386-nat.c:230: process to be compatible with the older Linux kernels.
next reply other threads:[~2013-02-14 2:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-14 2:00 GDB Administrator [this message]
2013-02-14 9:59 ` Pierre Muller
2013-02-14 11:27 ` Mark Kettenis
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=20130214015949.GA27541@sourceware.org \
--to=gdbadmin@sourceware.org \
--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