From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: Re: New ARI warning Sat Jan 10 01:54:00 UTC 2015
Date: Tue, 13 Jan 2015 10:48:00 -0000 [thread overview]
Message-ID: <1421146072-24296-1-git-send-email-brobecker@adacore.com> (raw)
In-Reply-To: <20150110015400.GA7237@sourceware.org>
This set of patches fixes 2 of the new ARI violations reported by
last Saturday's report. The other 2 should also be fixed, IMO
(use safe_strerror instead of strerror, because strerror may return
NULL for unknown errno), but is requires us to move safe_strerror
to the common area, knowning that there is one POSIX implementation
and a Windows one. So a little bit more work, left for another day.
The two patches were tested on x86_64-linux, and then pushed.
[PATCH 1/2] [ARI] Remove trailing new-line in argument of call to
[PATCH 2/2] [ARI] Remove trailing new-line in argument of call to
Thank you,
--
Joel
next prev parent reply other threads:[~2015-01-13 10:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-10 1:54 GDB Administrator
2015-01-13 10:48 ` Joel Brobecker [this message]
2015-01-13 10:48 ` [PATCH 1/2] [ARI] Remove trailing new-line in argument of call to warning Joel Brobecker
2015-01-13 10:48 ` [PATCH 2/2] " 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=1421146072-24296-1-git-send-email-brobecker@adacore.com \
--to=brobecker@adacore.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).