Mongodb doesn't work : inferior stopped, unknown signal
-
Hello everyone!,
I'm working on mongodbcxx with Qt Creator . I have a problem using the mongodb with Qt Creator: I create a simple Qt GUI application, I compile and I launch it very well, but if I launch it with the mongodb code, I receive that: my application mongo2.exe stopped working .
Then i tried with debugger mode then received signal recieved shown below ..
how to solve this ..??
Thanks in Advance.. -
still in mingw way problem not solved .
so i choose msvc compiler to do that .. so iam closing this ... -
Hi,
Did you check that the MongoDB dlls can be found when you start your application ?
-
@SGaist @ramonn334
Qt --Based on Qt 5.15.2 (MSVC 2019, 64 bit)
compiler - Mingw 8.1.0 64bit
-
@Vivek_A said in Mongodb doesn't work : inferior stopped, unknown signal:
Qt --Based on Qt 5.15.2 (MSVC 2019, 64 bit)
compiler - Mingw 8.1.0 64bitPlease do not mix-up the IDE (Qt Creator) version and the Qt-Kit version you are using to build your project.
What is important is the Qt Kit you are using to build the project.
The IDE those not matter, you can use Qt-Creator / MS Visual Code / Code-Blocks / etc. -
@Vivek_A said in Mongodb doesn't work : inferior stopped, unknown signal:
Qt --Based on Qt 5.15.2 (MSVC 2019, 64 bit)
That is likely Qt Creator informations
Because:
@Vivek_A said in Mongodb doesn't work : inferior stopped, unknown signal:
compiler - Mingw 8.1.0 64bit
You can't mix and match C++ libraries built with MinGW and Visual Studio.
So, again, did you ensure that your MongoDB dlls are found at run time ? They should either be copied in the same folder as where your executable is or in the Run part of the Project panel, modify the PATH environment variable and add the path where these dlls are.
-
@SGaist said in Mongodb doesn't work : inferior stopped, unknown signal:
MongoDB dlls are found at run time ?
how to see that ??? iam beginner.. i searched google .. didit found,
-
@Vivek_A said in Mongodb doesn't work : inferior stopped, unknown signal:
how to see that ??? iam beginner.. i searched google .. didit found,
@SGaist wrote:
They should either be copied in the same folder as where your executable is or in the Run part of the Project panel, modify the PATH environment variable and add the path where these dlls are.
?
-
You did what ?
I gave two different suggestions. -
@SGaist said in Mongodb doesn't work : inferior stopped, unknown signal:
They should either be copied in the same folder as where your executable is or in the Run part of the Project panel, modify the PATH environment variable and add the path where these dlls are
this 2 are tried , but still same problem , but the problem is only when instance creation,
when i tried a commandmongocxx::options::client client_options;
Now the error changed to ndll.dll
-
Did you try to build and run a simple MongoDB test app to see if you can get it to run ?
-
hi ..@SGaist @JonB . i Reinstalled mongocxx driver and then i started testing ref.(http://mongocxx.org/contributing/testing-mongocxx/
LD-RD2@LD-RD2 MINGW64 /C/Users/LD-RD2/AppData/Roaming/SPB_Data/mongo-cxx-driver-r3.6.5/cmake_build/src/mongocxx # make test Running tests... Test project C:/Users/LD-RD2/AppData/Roaming/SPB_Data/mongo-cxx-driver-r3.6.5/cmake_build/src/mongocxx Start 1: driver 1/11 Test #1: driver ...........................Exit code 0xc0000135 ***Exception: 0.07 sec Start 2: logging 2/11 Test #2: logging ..........................Exit code 0xc0000135 ***Exception: 0.03 sec Start 3: instance 3/11 Test #3: instance .........................Exit code 0xc0000135 ***Exception: 0.03 sec Start 4: crud_specs 4/11 Test #4: crud_specs .......................Exit code 0xc0000135 ***Exception: 0.03 sec Start 5: gridfs_specs 5/11 Test #5: gridfs_specs .....................Exit code 0xc0000135 ***Exception: 0.02 sec Start 6: client_side_encryption_specs 6/11 Test #6: client_side_encryption_specs .....Exit code 0xc0000135 ***Exception: 0.02 sec Start 7: command_monitoring_specs 7/11 Test #7: command_monitoring_specs .........Exit code 0xc0000135 ***Exception: 0.03 sec Start 8: change_stream_specs 8/11 Test #8: change_stream_specs ..............Exit code 0xc0000135 ***Exception: 0.02 sec Start 9: transactions_specs 9/11 Test #9: transactions_specs ...............Exit code 0xc0000135 ***Exception: 0.02 sec Start 10: retryable_reads_spec 10/11 Test #10: retryable_reads_spec .............Exit code 0xc0000135 ***Exception: 0.02 sec Start 11: read_write_concern_specs 11/11 Test #11: read_write_concern_specs .........Exit code 0xc0000135 ***Exception: 0.02 sec 0% tests passed, 11 tests failed out of 11 Total Test time (real) = 0.48 sec The following tests FAILED: 1 - driver (Exit code 0xc0000135 ) 2 - logging (Exit code 0xc0000135 ) 3 - instance (Exit code 0xc0000135 ) 4 - crud_specs (Exit code 0xc0000135 ) 5 - gridfs_specs (Exit code 0xc0000135 ) 6 - client_side_encryption_specs (Exit code 0xc0000135 ) 7 - command_monitoring_specs (Exit code 0xc0000135 ) 8 - change_stream_specs (Exit code 0xc0000135 ) 9 - transactions_specs (Exit code 0xc0000135 ) 10 - retryable_reads_spec (Exit code 0xc0000135 ) 11 - read_write_concern_specs (Exit code 0xc0000135 ) Errors while running CTest Output from these tests are in: C:/Users/LD-RD2/AppData/Roaming/SPB_Data/mongo-cxx-driver-r3.6.5/cmake_build/src/mongocxx/Testing/Temporary/LastTest.log Use "--rerun-failed --output-on-failure" to re-run the failed cases verbosely. make: *** [Makefile:136: test] Error 8
Test failed its all Exit code 0xc0000135.. ... help plz... how to fix ..
i
-
@Vivek_A
These all look like mongocxx issues, I don't see how a Qt user will know what the problems are. The error message clearly statesUse "--rerun-failed --output-on-failure" to re-run the failed cases verbosely.
There is a reason for output messages for the user to read, did you do this before asking for our help? I don't get why someone would not act on this....
-
@JonB i have already tried that , sry for not mentioning that ,
its saying -bash: --rerun-failed: command not foundadditionally i tried
make test VERBOSE=1 and ctest -R driver -VV
LD-RD2@LD-RD2 MINGW64 /C/Users/LD-RD2/AppData/Roaming/SPB_Data/mongo-cxx-driver-r3.6.5/cmake_build/src/mongocxx # ctest -R driver -VV UpdateCTestConfiguration from :C:/Users/LD-RD2/AppData/Roaming/SPB_Data/mongo-cxx-driver-r3.6.5/cmake_build/src/mongocxx/DartConfiguration.tcl UpdateCTestConfiguration from :C:/Users/LD-RD2/AppData/Roaming/SPB_Data/mongo-cxx-driver-r3.6.5/cmake_build/src/mongocxx/DartConfiguration.tcl Test project C:/Users/LD-RD2/AppData/Roaming/SPB_Data/mongo-cxx-driver-r3.6.5/cmake_build/src/mongocxx Constructing a list of tests Done constructing a list of tests Updating test list for fixtures Added 0 tests to meet fixture requirements Checking test dependency graph... Checking test dependency graph end test 1 Start 1: driver 1: Test command: C:\Users\LD-RD2\AppData\Roaming\SPB_Data\mongo-cxx-driver-r3.6.5\cmake_build\src\mongocxx\test\test_driver.exe 1: Environment variables: 1: ENCRYPTION_TESTS_PATH=C:/Users/LD-RD2/AppData/Roaming/SPB_Data/mongo-cxx-driver-r3.6.5/data/client_side_encryption 1: Test timeout computed to be: 10000000 1/1 Test #1: driver ...........................Exit code 0xc0000135 ***Exception: 0.03 sec 0% tests passed, 1 tests failed out of 1 Total Test time (real) = 0.05 sec The following tests FAILED: 1 - driver (Exit code 0xc0000135 ) Errors while running CTest Output from these tests are in: C:/Users/LD-RD2/AppData/Roaming/SPB_Data/mongo-cxx-driver-r3.6.5/cmake_build/src/mongocxx/Testing/Temporary/LastTest.log Use "--rerun-failed --output-on-failure" to re-run the failed cases verbosely.
-
@Vivek_A said in Mongodb doesn't work : inferior stopped, unknown signal:
its saying -bash: --rerun-failed: command not found
It does not say that
--rerun-failed --output-on-failure
is a Linux command, hence the error message. It is telling you to pass that as command-line arguments, to whatever command you use to run the tests... -
@Vivek_A said in Mongodb doesn't work : inferior stopped, unknown signal:
Exit code 0xc0000135
This usually means that a dll has not been found.
Can you explain exactly step by step what you did up to running the tests ?
-
still in mingw way problem not solved .
so i choose msvc compiler to do that .. so iam closing this ...