[Kmymoney-devel] [kmymoney4] [Bug 312692] Test #20: kmymoney-mymoneydatabasemgrtest FAILS FATALLY

Marko Käning mk-lists at email.de
Wed Feb 6 06:50:53 UTC 2013


https://bugs.kde.org/show_bug.cgi?id=312692

--- Comment #15 from Marko Käning <mk-lists at email.de> ---
I ran valgrind on this test and it failed right away. Looking into valgrind's
source code reveals the following comment:
---
   /* This may fail if the client stack is busted; if that happens,
      the whole process will exit rather than simply calling the
      signal handler. */
---
and that is what actually happens, BUT unfortunately I realized after all that
this is failing for ALL tests!!! :-( 
---
$ valgrind --leak-check=full  /opt/macports-test/bin/ctest
--force-new-ctest-process -R databasemgrtest -V
==52857== Memcheck, a memory error detector
==52857== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al.
==52857== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info
==52857== Command: /opt/macports-test/bin/ctest --force-new-ctest-process -R
databasemgrtest -V
==52857== 
UpdateCTestConfiguration  from
:/Users/marko/WC/GIT/kmymoney.mymoneydatabasemgrtest/build/DartConfiguration.tcl
UpdateCTestConfiguration  from
:/Users/marko/WC/GIT/kmymoney.mymoneydatabasemgrtest/build/DartConfiguration.tcl
Test project /Users/marko/WC/GIT/kmymoney.mymoneydatabasemgrtest/build
Constructing a list of tests
Done constructing a list of tests
Checking test dependency graph...
Checking test dependency graph end
test 20
    Start 20: kmymoney-mymoneydatabasemgrtest

20: Test command:
/Users/marko/WC/GIT/kmymoney.mymoneydatabasemgrtest/build/kmymoney/mymoney/storage/mymoneydatabasemgrtest.app/Contents/MacOS/mymoneydatabasemgrtest
20: Test timeout computed to be: 9.99988e+06

valgrind: m_signals.c:953 (handle_SCSS_change): Assertion 'ksa_old.sa_flags ==
skss_old.skss_per_sig[sig].skss_flags' failed.
==52861==    at 0x1380373F7: ???
==52861==    by 0x138037634: ???
==52861==    by 0x13804B175: ???
==52861==    by 0x13804D279: ???
==52861==    by 0x1380CC03B: ???
==52861==    by 0x1380A98C9: ???
==52861==    by 0x1380A7098: ???
==52861==    by 0x1380CE05F: ???

sched status:
  running_tid=1

Thread 1: status = VgTs_Runnable
==52861==    at 0x100A65032: __sigaction (in /usr/lib/libSystem.B.dylib)
==52861==    by 0x1002F7494: kwsysProcessCreate (in
/opt/macports-test/bin/ctest)
==52861==    by 0x1002F88F2: cmsysProcess_Execute (in
/opt/macports-test/bin/ctest)
==52861==    by 0x100026404: cmProcess::StartProcess() (in
/opt/macports-test/bin/ctest)
==52861==    by 0x10007908B: cmCTestRunTest::ForkProcess(double, bool,
std::vector<std::string, std::allocator<std::string> >*) (in
/opt/macports-test/bin/ctest)
==52861==    by 0x100079874: cmCTestRunTest::StartTest(unsigned long) (in
/opt/macports-test/bin/ctest)
==52861==    by 0x10007198B: cmCTestMultiProcessHandler::StartTestProcess(int)
(in /opt/macports-test/bin/ctest)
==52861==    by 0x100072384: cmCTestMultiProcessHandler::StartTest(int) (in
/opt/macports-test/bin/ctest)
==52861==    by 0x1000726B6: cmCTestMultiProcessHandler::StartNextTests() (in
/opt/macports-test/bin/ctest)
==52861==    by 0x1000727D0: cmCTestMultiProcessHandler::RunTests() (in
/opt/macports-test/bin/ctest)
==52861==    by 0x1000A0837:
cmCTestTestHandler::ProcessDirectory(std::vector<cmsys::String,
std::allocator<cmsys::String> >&, std::vector<cmsys::String,
std::allocator<cmsys::String> >&) (in /opt/macports-test/bin/ctest)
==52861==    by 0x1000A1F79: cmCTestTestHandler::ProcessHandler() (in
/opt/macports-test/bin/ctest)
==52861==    by 0x100012CDE: cmCTest::ProcessTests() (in
/opt/macports-test/bin/ctest)
==52861==    by 0x1000200A7: cmCTest::Run(std::vector<std::string,
std::allocator<std::string> >&, std::string*) (in /opt/macports-test/bin/ctest)
==52861==    by 0x10000AB0B: main (in /opt/macports-test/bin/ctest)


Note: see also the FAQ in the source distribution.
It contains workarounds to several common problems.
In particular, if Valgrind aborted or crashed after
identifying problems in your program, there's a good chance
that fixing those problems will prevent Valgrind aborting or
crashing, especially if it happened in m_mallocfree.c.

If that doesn't help, please report this bug to: www.valgrind.org

In the bug report, send all the above text, the valgrind
version, and what OS and version you are using.  Thanks.

1/1 Test #20: kmymoney-mymoneydatabasemgrtest ...***Failed    0.11 sec

0% tests passed, 1 tests failed out of 1

Total Test time (real) =   1.28 sec

The following tests FAILED:
     20 - kmymoney-mymoneydatabasemgrtest (Failed)
Errors while running CTest
==52857== 
==52857== HEAP SUMMARY:
==52857==     in use at exit: 327,984 bytes in 1,770 blocks
==52857==   total heap usage: 17,182 allocs, 15,412 frees, 2,197,080 bytes
allocated
==52857== 
==52857== 16 bytes in 1 blocks are definitely lost in loss record 93 of 399
==52857==    at 0x100662ABD: malloc (vg_replace_malloc.c:274)
==52857==    by 0x1009800CF: __cxa_get_globals (in
/usr/lib/libstdc++.6.0.9.dylib)
==52857==    by 0x10097FEA9: std::uncaught_exception() (in
/usr/lib/libstdc++.6.0.9.dylib)
==52857==    by 0x10095F096: std::ostream::sentry::~sentry() (in
/usr/lib/libstdc++.6.0.9.dylib)
==52857==    by 0x10095FBF9: std::basic_ostream<char, std::char_traits<char> >&
std::__ostream_insert<char, std::char_traits<char> >(std::basic_ostream<char,
std::char_traits<char> >&, char const*, long) (in
/usr/lib/libstdc++.6.0.9.dylib)
==52857==    by 0x10095FC57: std::basic_ostream<char, std::char_traits<char> >&
std::operator<< <std::char_traits<char> >(std::basic_ostream<char,
std::char_traits<char> >&, char const*) (in /usr/lib/libstdc++.6.0.9.dylib)
==52857==    by 0x10000B583: cmCTest::Log(int, char const*, int, char const*)
(in /opt/macports-test/bin/ctest)
==52857==    by 0x1000127D8: cmCTest::ProcessTests() (in
/opt/macports-test/bin/ctest)
==52857==    by 0x1000200A7: cmCTest::Run(std::vector<std::string,
std::allocator<std::string> >&, std::string*) (in /opt/macports-test/bin/ctest)
==52857==    by 0x10000AB0B: main (in /opt/macports-test/bin/ctest)
==52857== 
==52857== LEAK SUMMARY:
==52857==    definitely lost: 16 bytes in 1 blocks
==52857==    indirectly lost: 0 bytes in 0 blocks
==52857==      possibly lost: 0 bytes in 0 blocks
==52857==    still reachable: 320,465 bytes in 1,694 blocks
==52857==         suppressed: 7,503 bytes in 75 blocks
==52857== Reachable blocks (those to which a pointer was found) are not shown.
==52857== To see them, rerun with: --leak-check=full --show-reachable=yes
==52857== 
==52857== For counts of detected and suppressed errors, rerun with: -v
==52857== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 3 from 3)
---

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the KMyMoney-devel mailing list