Mongodb doesn't work : inferior stopped, unknown signal

Vivek_A · 25 Aug 2021, 07:32

@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,

JonB · 25 Aug 2021, 09:23

@Vivek_A said in Mongodb doesn't work : inferior stopped, unknown signal:

how to see that ??? iam beginner.. i searched google .. didit found,

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.

?

Vivek_A · J JonB 25 Aug 2021, 07:32

@JonB yes , i did that , but still same issue, iam attaching screenshot of the APP crash,

libbson-1.0.dll is part of mongo-c-driver, what to do next ..

SGaist · wrote on 25 Aug 2021, 19:18

You did what ?
I gave two different suggestions.

Vivek_A · S SGaist 25 Aug 2021, 06:26

@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 command

mongocxx::options::client client_options;

no error , is am wrong????

Now the error changed to ndll.dll

SGaist · wrote on 26 Aug 2021, 20:37

Did you try to build and run a simple MongoDB test app to see if you can get it to run ?

Vivek_A · 9 Feb 2021, 07:39

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

JonB · 9 Feb 2021, 08:34

@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 states

Use "--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....

Vivek_A · 9 Feb 2021, 09:01

@JonB i have already tried that , sry for not mentioning that ,
its saying -bash: --rerun-failed: command not found

additionally 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.

JonB · wrote on 2 Sept 2021, 10:13

@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...

SGaist · 6 Sept 2021, 08:50

@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 ?

Vivek_A · S SGaist 2 Sept 2021, 18:22

This post is deleted!

Vivek_A · wrote on 6 Sept 2021, 11:39

still in mingw way problem not solved .
so i choose msvc compiler to do that .. so iam closing this ...