[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [platform-testers] texinfo-6.5.90 pretest on Solaris 10

From: Gavin Smith
Subject: Re: [platform-testers] texinfo-6.5.90 pretest on Solaris 10
Date: Mon, 21 Jan 2019 20:30:05 +0000
User-agent: Mutt/1.5.23 (2014-03-12)

On Sun, Jan 20, 2019 at 05:13:05PM +0100, Bruno Haible wrote:
> > You could do "gdb perl core" with the core file
> Doesn't work: the 'perl' program and the 'core' file have no debugging
> information.

Maybe the core file is not compatible with the version of gdb.

> $ file core
> core:           ELF 32-bit LSB core file 80386 Version 1, from 'perl'
> $ perl --version
> This is perl, v5.8.4 built for i86pc-solaris-64int

It appears to be a 32-bit core file for a 64-bit operating system.

Maybe relevant: https://sourceware.org/bugzilla/show_bug.cgi?id=14944

Is there a 32-bit gdb installed that you could try using?

Another possiblity is to try using dbx instead of gdb.

Can you get texi2any to dump core without running it from the test suite?  If
so, you could pass "-c DEBUG=1" as a command-line option to give some
indication of where exactly it is failing.

> Rebuilt with cc (like last time), and with PERL_EXT_CFLAGS="-g". The result:
> 1) In the tp/tests/ directory: a 'core' file again and 20 test failures.
> "gdb /usr/bin/perl core" doesn't produce usable information either.
> 2) In the info/ directory, 2 tests fail. Find the log file attached.
> Rebuilt with gcc instead of cc, and with PERL_EXT_CFLAGS="-g". The result:
> 1) In the tp/tests/ directory, no 'core' file any more, all tests succeed.
> 2) In the info/ directory, 2 tests fail. Find the log file attached.

How did you use gcc instead of cc?  Was this by setting PERL_EXT_CC to 
'gcc'?  This would make sense if the Perl executable was itself compiled 
with gcc.  What is the output of "/usr/bin/perl -V:cc"?  We would want to
find why the TestXS.pm module works at configure-time but core is dumped 
later.  It could just be a fluke that TestXS.pm is compatible with the 
Perl executable even though it has been compiled with the wrong 

> > You could also export TEXINFO_XS=debug and run one of the test scripts, 
> > e.g. test_scripts/nested_formats_texi_nested_formats.sh from within the 
> > tp/tests directory.  (This is easier to do if you configured in-source: 
> > otherwise you have set a whole load of environment variables for this to 
> > work.)
> The Makefile sets the environment variables for me:
> $ TEXINFO_XS=debug gmake check 
> TESTS=test_scripts/nested_formats_texi_nested_formats.sh
> This run produces a couple of files, which you find attached, and a 'core' 
> file,
> which is too large to attach.

Thanks, it appears that the XS parser module is not being loaded, so the 
problem is with one of the other XS modules (that were present in 
previous Texinfo releases).

The info test failures look like the program has been timed out for not
finishing quickly enough.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]