This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: GDB 7.10 release 2015-07-17 status update?
- From: Pedro Alves <palves at redhat dot com>
- To: Eli Zaretskii <eliz at gnu dot org>, Luis Machado <lgustavo at codesourcery dot com>
- Cc: brobecker at adacore dot com, gdb-patches at sourceware dot org, keiths at redhat dot com, jan dot kratochvil at redhat dot com, yunlian at google dot com
- Date: Fri, 24 Jul 2015 10:26:16 +0100
- Subject: Re: GDB 7.10 release 2015-07-17 status update?
- Authentication-results: sourceware.org; auth=none
- References: <20150717175328 dot GA15874 at adacore dot com> <55A94617 dot 1040701 at codesourcery dot com> <83r3o661z4 dot fsf at gnu dot org>
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?
Thanks,
Pedro Alves