Jose E. Marchesi wrote:
> I think in this case it is better to not use the xalloc module in
> libpoke at all.
This looks feasible: There are not many references to functions like
xmalloc in libpoke.
pkl-ast.c:116: PKL_AST_STRING_POINTER (new) = xstrdup (str);
pkl-ast.c:131: PKL_AST_IDENTIFIER_P
> Hannes Domani wrote:
>> When I'm trying to (statically) link libpoke into gdb, I get the following
>> errors:
>>
>> ... gl-libpoke/xmalloc.c:44: multiple definition of `xmalloc'; alloc.o
>> ... gdb/alloc.c:49: first defined here
>>
>
Hannes Domani wrote:
> When I'm trying to (statically) link libpoke into gdb, I get the following
> errors:
>
> ... gl-libpoke/xmalloc.c:44: multiple definition of `xmalloc'; alloc.o
> ... gdb/alloc.c:49: first defined here
>
> Both gdb and gl-libpoke define the
Hello
When I'm trying to (statically) link libpoke into gdb, I get the following
errors:
c:/msys64/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/11.2.0/../../../../x86_64-w64-mingw32/bin/ld.exe:
C:/src/repos/poke/inst/lib/libpoke.a(libgnu_la-xmalloc.o): in function
`xmalloc':
C:\src\
Enze Li wrote:
> > PR build/28413 notes that the gdb master fails to build on macOS.
The build fails due to the combination of '-Werror' and a useful
warning emitted by Gnulib.
But Gnulib does not support '-Werror'. To fix the issue, you need to
filter out the '-W
[ add bug-gnulib@gnu.org ]
On 10/4/21 6:03 PM, Enze Li via Gdb-patches wrote:
> PR build/28413 notes that the gdb master fails to build on macOS.
>
> Based on De Morgan's law, the expression
> !(defined __GNUC__ && !defined __clang__ && __OPTIMIZE__)
> is eq
Eli Zaretskii wrote in
<https://lists.gnu.org/archive/html/bug-gnulib/2021-03/msg00135.html>:
> The following snippet from Gnulib's unistd.h causes a compilation
> error when building the current development version of GDB 11:
>
> #if @GNULIB_MDA_SWAB@
> /* On nat
The following snippet from Gnulib's unistd.h causes a compilation
error when building the current development version of GDB 11:
#if @GNULIB_MDA_SWAB@
/* On native Windows, map 'swab' to '_swab', so that -loldnames is not
required. In C++ with GNULIB_NAMESPACE,
Eric Blake wrote:
> > There still is a crash in test-duplocale. It occurs in
> > main (test-duplocale.c:100)
> > -> get_locale_dependent_values (test-duplocale.c:45)
> > -> strfmon
> >
> > I'm using Cygwin 2.6.1(0.305/5/3) 2016-12-16 11:55
The gnulib configure machinery doesn't take into account cross-builds.
I ran into this while doing a cross-build of GDB. It broke badly on a
build=X86_64-linux, host=i386-netbsdelf cross-build, because Linux attempted to
execute the generated conftest image (a NetBSD image). That&#x
On 08/25/2015 06:06 PM, paul_kon...@dell.com wrote:
>
>> On Aug 25, 2015, at 12:58 PM, Paul Eggert wrote:
>>
>> Pedro Alves wrote:
>>> # Test for the AIX locale name.
if (LC_ALL=ja_JP LC_TIME= LC_CTYPE= ./conftest; exit)
2>/dev/null; then
gt_cv_locale
> On Aug 25, 2015, at 12:58 PM, Paul Eggert wrote:
>
> Pedro Alves wrote:
>> # Test for the AIX locale name.
>>> if (LC_ALL=ja_JP LC_TIME= LC_CTYPE= ./conftest; exit) 2>/dev/null;
>>> then
>>>gt_cv_locale_ja=ja_JP
>>>
>>> The comment refers to AIX, but it is in f
> On Aug 25, 2015, at 12:58 PM, Paul Eggert wrote:
>
> Pedro Alves wrote:
>> # Test for the AIX locale name.
>>> if (LC_ALL=ja_JP LC_TIME= LC_CTYPE= ./conftest; exit) 2>/dev/null;
>>> then
>>>gt_cv_locale_ja=ja_JP
>>>
>>> The comment refers to AIX, but it is in f
Pedro Alves wrote:
# Test for the AIX locale name.
if (LC_ALL=ja_JP LC_TIME= LC_CTYPE= ./conftest; exit) 2>/dev/null;
then
gt_cv_locale_ja=ja_JP
The comment refers to AIX, but it is in fact executed in the "*" case of a case
statement, i.e., for everything oth
Adding gnulib@
Original thread here:
https://sourceware.org/ml/gdb/2015-08/msg00037.html
Thanks,
Pedro Alves
On 08/25/2015 02:12 PM, paul_kon...@dell.com wrote:
>
>> On Aug 25, 2015, at 5:56 AM, Pedro Alves wrote:
>>
>> On 08/24/2015 10:20 PM, paul_kon...@dell.com wrote:
Hi,
When i start with # gdb test-fflush
GDB is free software and you are welcome to distribute copies of it
under certain conditions; type "show copying" to see the conditions.
There is absolutely no warranty for GDB; type "show warranty" for details.
GDB 4.16 (emx),
Bruno Haible <[EMAIL PROTECTED]> wrote:
> Jim Meyering wrote:
>> I did not set errno, which would normally happen for a real failure.
>> I tried, but __errno_location() returns an invalid address.
>> Anyone know how to set errno via gdb?
>
> I normally use
>
Jim Meyering wrote:
> I did not set errno, which would normally happen for a real failure.
> I tried, but __errno_location() returns an invalid address.
> Anyone know how to set errno via gdb?
I normally use
(gdb) print errno = 22
since in a single-threaded situation __errno
18 matches
Mail list logo
