octave-maintainers
[Top][All Lists]
Advanced

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

Re: Segfault when running "make check"


From: Julien Bect
Subject: Re: Segfault when running "make check"
Date: Wed, 30 Jan 2013 21:13:09 +0100
User-agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130106 Thunderbird/17.0.2

On 30/01/2013 20:55, Jordi Gutiérrez Hermoso wrote:
On 30 January 2013 14:53, Julien Bect <address@hidden> wrote:
On 30/01/2013 20:40, Mike Miller wrote:
What version of gcc/g++/gfortran are you using and on which architecture?
gcc version 4.7.2 (Ubuntu/Linaro 4.7.2-2ubuntu1) Target: i686-linux-gnu
Can you try running make check with valgrind? This may be slow and will produce piles upon piles of output, though... - Jordi G. H.

Here is the output (please tell me if I don't use the appropriate options for valgrind) :

$ valgrind --leak-check=full make -C test check
==9740== Memcheck, a memory error detector
==9740== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
==9740== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
==9740== Command: make -C test check
==9740==
make: Entering directory `/media/data/sources/octave/test'
../run-octave --norc --silent --no-history ./fntests.m .

Integrated test scripts:

  libinterp/corefcn/__contourc__.cc ...................... PASS    1/1  
  libinterp/corefcn/__dispatch__.cc ...................... PASS    1/1
  ...
  scripts/general/cumtrapz.m ............................. PASS    9/9  
  scripts/general/curl.m ................................. PASS    1/1  
  scripts/general/dblquad.m ..............................make: *** [check] Segmentation fault (core dumped)
make: Leaving directory `/media/data/sources/octave/test'
==9740==
==9740== HEAP SUMMARY:
==9740==     in use at exit: 262,717 bytes in 8,102 blocks
==9740==   total heap usage: 25,664 allocs, 17,562 frees, 1,545,849 bytes allocated
==9740==
==9740== 2 bytes in 1 blocks are definitely lost in loss record 1,061 of 3,048
==9740==    at 0x402BB7A: malloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
==9740==    by 0x8059D18: ??? (in /usr/bin/make)
==9740==    by 0x804A84D: ??? (in /usr/bin/make)
==9740==    by 0x40794D2: (below main) (libc-start.c:226)
==9740==
==9740== 3 bytes in 1 blocks are possibly lost in loss record 1,093 of 3,048
==9740==    at 0x402BB7A: malloc (in /usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
==9740==    by 0x8059D18: ??? (in /usr/bin/make)
==9740==    by 0x8059DC2: ??? (in /usr/bin/make)
==9740==    by 0x805990F: ??? (in /usr/bin/make)
==9740==    by 0x804A84D: ??? (in /usr/bin/make)
==9740==    by 0x40794D2: (below main) (libc-start.c:226)
==9740==
==9740== LEAK SUMMARY:
==9740==    definitely lost: 2 bytes in 1 blocks
==9740==    indirectly lost: 0 bytes in 0 blocks
==9740==      possibly lost: 3 bytes in 1 blocks
==9740==    still reachable: 262,712 bytes in 8,100 blocks
==9740==         suppressed: 0 bytes in 0 blocks
==9740== Reachable blocks (those to which a pointer was found) are not shown.
==9740== To see them, rerun with: --leak-check=full --show-reachable=yes
==9740==
==9740== For counts of detected and suppressed errors, rerun with: -v
==9740== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0)


reply via email to

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