From: Luis Machado <lgustavo@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: New ARI warning Fri Aug 23 01:51:51 UTC 2013 in -D 2013.08.23.00.00.15
Date: Fri, 23 Aug 2013 02:37:00 -0000 [thread overview]
Message-ID: <5216CAE0.8020505@codesourcery.com> (raw)
In-Reply-To: <20130823015151.GA1807@sourceware.org>
On 08/22/2013 10:51 PM, GDB Administrator wrote:
> 128a129,132
>> gdb/common/linux-ptrace.c:258: regression: hash: Do not use ' #...', instead use '#...'(some compilers only correctly parse a C preprocessor directive when '#' is the first character on the line)
> gdb/common/linux-ptrace.c:258: #ifdef __ia64__
>> gdb/common/linux-ptrace.c:261: regression: hash: Do not use ' #...', instead use '#...'(some compilers only correctly parse a C preprocessor directive when '#' is the first character on the line)
> gdb/common/linux-ptrace.c:261: #else
>> gdb/common/linux-ptrace.c:264: regression: hash: Do not use ' #...', instead use '#...'(some compilers only correctly parse a C preprocessor directive when '#' is the first character on the line)
> gdb/common/linux-ptrace.c:264: #endif
>> gdb/common/linux-ptrace.c:448: gettext: _ markup: All messages should be marked up with _.
> gdb/common/linux-ptrace.c:448: warning ("linux_check_ptrace_features: failed to kill child");
> 377d380
> < gdb/linux-nat.c:480: gettext: _ markup: All messages should be marked up with _.
> gdb/linux-nat.c:480: warning ("linux_test_for_tracefork: failed to kill child");
>
>
I've committed an obvious fix for these.
http://sourceware.org/ml/gdb-cvs/2013-08/msg00119.html
prev parent reply other threads:[~2013-08-23 2:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-23 1:51 GDB Administrator
2013-08-23 2:37 ` Luis Machado [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=5216CAE0.8020505@codesourcery.com \
--to=lgustavo@codesourcery.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