From: Iain Buclaw <ibuclaw@gdcproject.org>
To: Pedro Alves <palves@redhat.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
Luis Machado <lgustavo@codesourcery.com>,
Joel Brobecker <brobecker@adacore.com>,
GDB Patches <gdb-patches@sourceware.org>,
keiths@redhat.com, Jan Kratochvil <jan.kratochvil@redhat.com>,
Yunlian Jiang <yunlian@google.com>
Subject: Re: GDB 7.10 release 2015-07-17 status update?
Date: Fri, 24 Jul 2015 14:31:00 -0000 [thread overview]
Message-ID: <CABOHX+fN=PHd4AiY8MmP0jAoENyOw8_LU388hfiPdWEP4O9C4Q@mail.gmail.com> (raw)
In-Reply-To: <55B204B8.9030101@redhat.com>
On 24 July 2015 at 11:26, Pedro Alves <palves@redhat.com> wrote:
> On 07/17/2015 08:03 PM, Eli Zaretskii wrote:
>>> Date: Fri, 17 Jul 2015 15:14:47 -0300
>>> From: Luis Machado <lgustavo@codesourcery.com>
>>> CC: <keiths@redhat.com>, Jan Kratochvil <jan.kratochvil@redhat.com>, <yunlian@google.com>
>>>
>>> Do we consider the fact that mingw32 (and maybe other non-GNU) builds
>>> have been broken since this libiberty sync a blocker/critical issue?
>>
>> It's not broken: I've built the pretest with that problem in it, and
>> it does build, albeit with a (harmless) warning.
>>
>>> Last we heard of it was here...
>>>
>>> https://sourceware.org/ml/gdb-patches/2015-06/msg00654.html
>>
>> The release tarball builds without -Werror, so this warning is just a
>> warning, since asprintf does return an int.
>
> It's also a varargs function though; varargs functions
> must have a visible prototype. I wouldn't be surprised if this
> resulted in a crash/corruption on some targets/abis.
>
> ISTR seeing a patch for this, but I can't find it now.
>
> Did I just imagine it?
>
Do you mean: https://sourceware.org/ml/gdb-patches/2015-07/msg00570.html
Iain
next prev parent reply other threads:[~2015-07-24 14:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-17 17:53 Joel Brobecker
2015-07-17 18:14 ` Luis Machado
2015-07-17 18:32 ` Joel Brobecker
2015-07-17 18:38 ` Luis Machado
2015-07-17 19:06 ` Eli Zaretskii
2015-07-17 20:48 ` Joel Brobecker
2015-07-17 20:57 ` Luis Machado
2015-07-20 10:13 ` Iain Buclaw
2015-07-21 17:16 ` Joel Brobecker
2015-07-17 19:04 ` Eli Zaretskii
2015-07-17 19:03 ` Eli Zaretskii
2015-07-24 9:26 ` Pedro Alves
2015-07-24 14:31 ` Iain Buclaw [this message]
2015-07-24 14:37 ` Pedro Alves
2015-07-17 18:25 ` Keith Seitz
2015-07-17 18:28 ` Jan Kratochvil
2015-07-17 18:35 ` Joel Brobecker
2015-07-17 20:15 ` Simon Marchi
2015-07-17 20:57 ` Joel Brobecker
2015-07-17 21:00 ` Simon Marchi
2015-07-17 20:24 ` Sergio Durigan Junior
2015-07-20 10:06 ` Yao Qi
2015-07-21 17:11 ` 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='CABOHX+fN=PHd4AiY8MmP0jAoENyOw8_LU388hfiPdWEP4O9C4Q@mail.gmail.com' \
--to=ibuclaw@gdcproject.org \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=keiths@redhat.com \
--cc=lgustavo@codesourcery.com \
--cc=palves@redhat.com \
--cc=yunlian@google.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