Git Product home page Git Product logo

Comments (13)

0xFFFC0000 avatar 0xFFFC0000 commented on June 16, 2024

Can you enable the log and put here the detailed output? I believe something like this would do it for you after building:

$ctest -R core_tests --debug

from monero.

qnfm avatar qnfm commented on June 16, 2024

Can you enable the log and put here the detailed output? I believe something like this would do it for you after building:

$ctest -R core_tests --debug

/home/username/sda/lsf/cmake-3.21.2/Source/cmCTest.cxx:420 Here: 420

/home/username/sda/lsf/cmake-3.21.2/Source/cmCTest.cxx:706 UpdateCTestConfiguration from :/home/username/dev/monero/build/tests/core_tests/DartConfiguration.tcl

/home/username/sda/lsf/cmake-3.21.2/Source/cmCTest.cxx:432 Here: 432

/home/username/sda/lsf/cmake-3.21.2/Source/cmCTest.cxx:3001 * Read custom CTest configuration directory: /home/username/dev/monero/build/tests/core_tests

/home/username/sda/lsf/cmake-3.21.2/Source/cmCTest.cxx:3004 * Check for file: /home/username/dev/monero/build/tests/core_tests/CTestCustom.cmake

/home/username/sda/lsf/cmake-3.21.2/Source/cmCTest.cxx:3024 * Check for file: /home/username/dev/monero/build/tests/core_tests/CTestCustom.ctest

/home/username/sda/lsf/cmake-3.21.2/Source/cmCTest.cxx:706 UpdateCTestConfiguration from :/home/username/dev/monero/build/tests/core_tests/DartConfiguration.tcl

/home/username/sda/lsf/cmake-3.21.2/Source/CTest/cmCTestTestHandler.cxx:401 Test project /home/username/dev/monero/build/tests/core_tests

/home/username/sda/lsf/cmake-3.21.2/Source/CTest/cmCTestTestHandler.cxx:1761 Constructing a list of tests

/home/username/sda/lsf/cmake-3.21.2/Source/CTest/cmCTestTestHandler.cxx:2424 Add test: core_tests

/home/username/sda/lsf/cmake-3.21.2/Source/CTest/cmCTestTestHandler.cxx:2468 Set test directory: /home/username/dev/monero/build/tests/core_tests

/home/username/sda/lsf/cmake-3.21.2/Source/CTest/cmCTestTestHandler.cxx:1813 Done constructing a list of tests

/home/username/sda/lsf/cmake-3.21.2/Source/CTest/cmCTestTestHandler.cxx:957 Updating test list for fixtures

/home/username/sda/lsf/cmake-3.21.2/Source/CTest/cmCTestTestHandler.cxx:1182 Added 0 tests to meet fixture requirements

/home/username/sda/lsf/cmake-3.21.2/Source/cmCTest.cxx:306 Current_Time: Dec 26 07:04 CST

/home/username/sda/lsf/cmake-3.21.2/Source/cmCTest.cxx:306 Current_Time: Dec 26 07:04 CST

/home/username/sda/lsf/cmake-3.21.2/Source/CTest/cmCTestMultiProcessHandler.cxx:1411 Checking test dependency graph...

/home/username/sda/lsf/cmake-3.21.2/Source/CTest/cmCTestMultiProcessHandler.cxx:1440 Checking test dependency graph end

/home/username/sda/lsf/cmake-3.21.2/Source/CTest/cmCTestMultiProcessHandler.cxx:168 test 1

/home/username/sda/lsf/cmake-3.21.2/Source/CTest/cmCTestRunTest.cxx:503 Start 1: core_tests

/home/username/sda/lsf/cmake-3.21.2/Source/CTest/cmCTestRunTest.cxx:670
1: Test command: /home/username/dev/monero/build/tests/core_tests/core_tests "--generate_and_play_test_data"

/home/username/sda/lsf/cmake-3.21.2/Source/cmCTest.cxx:306 Current_Time: Dec 26 07:04 CST

/home/username/sda/lsf/cmake-3.21.2/Source/CTest/cmCTestRunTest.cxx:736 1: Test timeout computed to be: 10000000

/home/username/sda/lsf/cmake-3.21.2/Source/CTest/cmCTestRunTest.cxx:888 1/1 Test #1: core_tests .......................
/home/username/sda/lsf/cmake-3.21.2/Source/CTest/cmCTestRunTest.cxx:892 Testing core_tests ...
/home/username/sda/lsf/cmake-3.21.2/Source/CTest/cmCTestRunTest.cxx:237 ***Exception: SegFault 0.26 sec

/home/username/sda/lsf/cmake-3.21.2/Source/cmCTest.cxx:306 Current_Time: Dec 26 07:04 CST

/home/username/sda/lsf/cmake-3.21.2/Source/cmCTest.cxx:306 Current_Time: Dec 26 07:04 CST

/home/username/sda/lsf/cmake-3.21.2/Source/cmCTest.cxx:306 Current_Time: Dec 26 07:04 CST

/home/username/sda/lsf/cmake-3.21.2/Source/CTest/cmCTestTestHandler.cxx:605
0% tests passed, 1 tests failed out of 1

/home/username/sda/lsf/cmake-3.21.2/Source/CTest/cmCTestTestHandler.cxx:617
Total Test time (real) = 0.26 sec

/home/username/sda/lsf/cmake-3.21.2/Source/CTest/cmCTestTestHandler.cxx:656
The following tests FAILED:

/home/username/sda/lsf/cmake-3.21.2/Source/CTest/cmCTestTestHandler.cxx:674 1 - core_tests (SEGFAULT)

/home/username/sda/lsf/cmake-3.21.2/Source/cmCTest.cxx:2907 Running a test(s) failed returning : 8

from monero.

selsta avatar selsta commented on June 16, 2024

Can you start core_tests in gdb and share a backtrace?

from monero.

0xFFFC0000 avatar 0xFFFC0000 commented on June 16, 2024

Two other things I am suspicious of.

  1. Running core_tests without any initialization, I believe does not work. For example, if I run ./core_tests it does print:
$ >> ./core_tests 
2023-12-26 08:35:04.770	E Wrong arguments
  1. When you run ctest -R core_tests --debug it should dump much more dump than only CMake. I f the core_tests runs. This means for some reason it gets SIGSEGV at the very beginning.

from monero.

qnfm avatar qnfm commented on June 16, 2024

Before I check with gdb, I changed the build option CMAKE_BUILD_TYPE to Debug, it gave me the expected test output.

cmake -GNinja -S. -Bbuild -DCMAKE_BUILD_TYPE=Debug -DBUILD_TESTS=ON && cmake --build build

The core_tests --generate_and_play_test_data finally produce the right output.

Without the flag, the backtrace is

Reading symbols from ./core_tests...done.
(gdb) run
Starting program: /home/hfutzny/Music/monero/build/tests/core_tests/core_tests --generate_and_play_test_data
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0x00005555556899fa in main ()
(gdb) backtrace
#0  0x00005555556899fa in main ()
(gdb) 

from monero.

qnfm avatar qnfm commented on June 16, 2024

How about change this part

if(BUILD_DEBUG_UTILITIES)
  add_subdirectory(debug_utilities)
endif()

into

if(BUILD_DEBUG_UTILITIES OR BUILD_TESTS)
  add_subdirectory(debug_utilities)
endif()

from monero.

0xFFFC0000 avatar 0xFFFC0000 commented on June 16, 2024

This doesn't look like correct to me. Can you use list command in gdb to show which line exactly the SIGSEGV happens?

from monero.

qnfm avatar qnfm commented on June 16, 2024

This doesn't look like correct to me. Can you use list command in gdb to show which line exactly the SIGSEGV happens?

Here is the output:

hfutzny@hfutzny-SYS-4029GP-TRT2:/tmp/monero$ gdb --args build/tests/core_tests/core_tests --generate_and_play_test_data
Reading symbols from build/tests/core_tests/core_tests...done.
(gdb) run
Starting program: /tmp/monero/build/tests/core_tests/core_tests --generate_and_play_test_data
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0x000055555566e8ea in main ()
(gdb) list
1	<built-in>: No such file or directory.
(gdb) backtrace 
#0  0x000055555566e8ea in main ()
(gdb) 

from monero.

0xFFFC0000 avatar 0xFFFC0000 commented on June 16, 2024

It still doesn't make sense to me. Looks like a linking/library issue for some reason. I will take a look at this.

from monero.

cecuabin avatar cecuabin commented on June 16, 2024

(cfdm^+1/2e+lt1)* = dtt^2 +1/2-4/3.15.dmb
GPI + K3.105^n = R^2*.rsc
dt= 2/3 -icsg8 . pi^2*.int
gu=dd1t1cs^2d2-DT9t'.lk
Ka = rc^muv^sh2-pu^2/Eccp^8''
.zip
W1^3/2 + d1t1 . w^3/2 = $LUNC + target 300dsh ($0.023)
RB + MAF = Eo - d1t1 . wrs^2|/^o,313

from monero.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.