I have attached a bzip2 compressed log of a complete walk through the failing test-vasprintf-posix on darwin12 for a build at -O0 -g. The backtrace for this failure looks like...
# gdb ./test-vasprintf-posix
GNU gdb 6.3.50-20050815 (Apple version gdb-1824) (Wed Feb 6 22:51:23 UTC 2013)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or 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.
This GDB was configured as "x86_64-apple-darwin"...Reading symbols for shared
libraries .. done
(gdb) break fancy_abort
Function "fancy_abort" not defined.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 1 (fancy_abort) pending.
(gdb) display/i $pc
(gdb) r
Starting program:
/sw/src/fink.build/m4-1.4.16-3/m4-1.4.16/tests/test-vasprintf-posix
Reading symbols for shared libraries +.............................. done
test-vasprintf-posix.c:237: assertion failed
Program received signal SIGABRT, Aborted.
0x00007fff985b6d46 in __kill ()
1: x/i $pc 0x7fff985b6d46 <__kill+10>: jae 0x7fff985b6d4d <__kill+17>
(gdb) bt
#0 0x00007fff985b6d46 in __kill ()
#1 0x00007fff8fa70df0 in abort ()
#2 0x0000000100001d35 in test_function (my_asprintf=0x10001f130 <my_asprintf>)
at test-vasprintf-posix.c:234
#3 0x000000010001f120 in test_vasprintf () at test-vasprintf-posix.c:3648
#4 0x00000001000008ab in main (argc=1, argv=0x7fff5fbff7a0) at
test-vasprintf-posix.c:3660
(gdb)
Hopefully this and log will help define the origin of the bug (ie whether Apple
has
defective printf supports the 'a' and 'A' directives or if the m4 code is
making incorrect
assumptions about this support). Thanks in advance.
Jack
test-vasprintf-posix_darwin12_gdb_walk.log.bz2
Description: BZip2 compressed data
