Re: segfault during test

[Rik]

On 08/02/2012 04:59 AM, JuanPi wrote:
> On Wed, Aug 1, 2012 at 6:13 PM, Rik <address@hidden> wrote:
>> On 08/01/2012 08:39 AM, JuanPi wrote:
>>> On Wed, Aug 1, 2012 at 5:26 PM, Rik <address@hidden> wrote:
>>>> On 08/01/2012 07:40 AM, address@hidden wrote:
>>>>> Message: 2
>>>>> Date: Wed, 1 Aug 2012 14:02:13 +0200
>>>>> From: JuanPi <address@hidden>
>>>>> To: Octave Maintainers <address@hidden>
>>>>> Subject: Fresh build segfault
>>>>> Message-ID:
>>>>>       <address@hidden>
>>>>> Content-Type: text/plain; charset=ISO-8859-1
>>>>>
>>>>> Hi all,
>>>>>
>>>>> Compiling on a fresh checkout I get a segmentation fault when running
>>>>> "make check" (configured with "./configure" with no flags)
>>>>>
>>>>> Summary:
>>>>>
>>>>>   PASS     10472
>>>>>   FAIL         1
>>>>>   XFAIL        3
>>>>>
>>>>> See the file test/fntests.log for additional details.
>>>>>
>>>>> Expected failures (listed as XFAIL above) are known bugs.
>>>>> Please help improve Octave by contributing fixes for them.
>>>>>
>>>>> 356 (of 934) .m files have no tests.
>>>>>
>>>>> 0 (of 121) .cc files have no tests.
>>>>>
>>>>> Please help improve Octave by contributing tests for
>>>>> these files (see the list in the file fntests.log).
>>>>>
>>>>> panic: Segmentation fault -- stopping myself...
>>>>> panic: attempted clean up apparently failed -- aborting...
>>>>> panic: attempted clean up apparently failed -- aborting...
>>>>> attempting to save variables to `octave-workspace'...
>>>>> panic: attempted clean up apparently failed -- aborting...
>>>>> make[1]: *** [check] Aborted (core dumped)
>>>>> make[1]: Leaving directory `/home/juanpi/Projects/octave-dev/test'
>>>>> make: *** [check] Error 2
>>>>>
>>>>> Any ideas what can be causing this?
>>>> 8/1/12
>>>>
>>>> Juan,
>>>>
>>>> I would guess that you might have cruft left over from a previous build.
>>>> For example, with the recent change to the src/ directory tree it is
>>>> possible that you have dynamically linked functions in the DLD-FUNCTIONS
>>>> directory as well as the the built-in versions in the new corefcns
>>>> directory.  It is possible that Octave is pulling in an old version of a
>>>> function which may have been compiled with different options, etc.
>>>>
>>>> I would try the following from the top-level directory:
>>>> make maintainer-clean   # remove all built objects
>>>> find . -name '*.lo'    # find any library objects.  These should be 
>>>> deleted.
>>>> find . -name '*.la'    # find any library archives.  These should be 
>>>> deleted.
>>>> find . -name '*.df'    # find any definition files.  These should be 
>>>> deleted.
>>>>
>>>> Then run the complete build cycle again
>>>> ./autogen.sh
>>>> ./configure
>>>> make
>>>>
>>>> --Rik
>>> Can that be? I am compiling in a repo that was checked out from scratch.
>> No.  A brand new repo shouldn't have any cruft.  Is this a plain install on
>> a Linux machine?
>>
>> --Rik
> Hi,
> The OS is
> Ubuntu 12.04 LTS (GNU/Linux 3.2.0-27-generic x86_64)
>
> gcc is
> gcc (Ubuntu/Linaro 4.6.3-1ubuntu5) 4.6.3
>
> The segfault happens after all test are finished.
>
8/2/12

Juan,

It looks like all the easy channels for debug are closed. 

I would start by configuring a debug build of Octave with CFLAGS '-g -O0'. 
When you have that built, run it under gdb with './run-octave -g'.
This will put you at the gdb prompt.  Type 'run' to start Octave.
When Octave has started, type 'cd test' and then 'fntests'
This will start the integrated test suite usually run by 'make check'.  If
you have separate build and src directories you will need to cd to the
actual location of fntests.m to run it.
When the tests have completed type 'exit'.  Hopefully you will produce a
segfault at that time and you can use the various facilities of gdb such as
'bt' for backtrace to see where in the Octave internals the problem came from.

--Rik