On Sun, Jan 27, 2008 at 10:33:20AM -0800, James Keenan via RT wrote:
> On Sun Jan 27 09:36:26 2008, [EMAIL PROTECTED] wrote:
> > Hi.
> >
> > The test for the backtrace() function was failing
>
>
> Could you post the failing test result?
>
> In particular, the output of 'prove -v t/steps/auto_backtrace*.t' would
> be helpful.
>
> I haven't seen any failures in these tests lately, so I'm unclear as to
> what failures you're trying to correct with your patch.
>
> Thank you very much.
>
Hi.
Here's the relevant configuration step output with '--verbose=2'.
Unpatched code produces:
Determining whether libc has the backtrace* functions (glibc only)...
gcc -D_REENTRANT -D_GNU_SOURCE -pipe -I/usr/local/include -I/opt/gnu/include
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include/gdbm -I./include -c
test.c
test.c:7: error: conflicting types for 'backtrace'
/usr/include/execinfo.h:28: error: previous declaration of 'backtrace' was here
test.c:8: error: conflicting types for 'backtrace_symbols'
/usr/include/execinfo.h:33: error: previous declaration of 'backtrace_symbols'
was here
......no.
With my patch the output is ...
Determining whether libc has the backtrace* functions (glibc only)...
gcc -D_REENTRANT -D_GNU_SOURCE -pipe -I/usr/local/include -I/opt/gnu/include
-D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/include/gdbm -I./include -c
test.c
gcc -L/usr/local/lib -L/opt/gnu/lib -Wl,-E test.o -o test -lnsl -ldl -lm
-lcrypt -lutil -lpthread
Setting Configuration Data:
(
glibc_backtrace => '1',
);
.....yes.
This is on my Debian "sid" system - 'gcc' is version 4.2.2-7 of the
'gcc-4.2' package, my libc is version 2.7-6 of the 'libc6' package.
Art Haas
--
Man once surrendering his reason, has no remaining guard against absurdities
the most monstrous, and like a ship without rudder, is the sport of every wind.
-Thomas Jefferson to James Smith, 1822
