Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. Mongodb doesn't work : inferior stopped, unknown signal
Forum Updated to NodeBB v4.3 + New Features

Mongodb doesn't work : inferior stopped, unknown signal

Scheduled Pinned Locked Moved Solved General and Desktop
c++qt5mongodbqt creator
19 Posts 5 Posters 2.6k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • Vivek_AV Vivek_A

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

    JonBJ Offline
    JonBJ Offline
    JonB
    wrote on last edited by
    #8

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

    ?

    Vivek_AV 1 Reply Last reply
    0
    • JonBJ JonB

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

      ?

      Vivek_AV Offline
      Vivek_AV Offline
      Vivek_A
      wrote on last edited by Vivek_A
      #9

      @JonB yes , i did that , but still same issue, iam attaching screenshot of the APP crash,
      9561372b-7541-42cf-a9c9-ebca6f434d22-image.png

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

      1 Reply Last reply
      0
      • SGaistS Offline
        SGaistS Offline
        SGaist
        Lifetime Qt Champion
        wrote on last edited by
        #10

        You did what ?
        I gave two different suggestions.

        Interested in AI ? www.idiap.ch
        Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

        1 Reply Last reply
        0
        • SGaistS SGaist

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

          Vivek_AV Offline
          Vivek_AV Offline
          Vivek_A
          wrote on last edited by Vivek_A
          #11

          @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????
          ce1e4a67-a41b-4f4a-a047-a86af24813a3-image.png

          Now the error changed to ndll.dll

          1 Reply Last reply
          0
          • SGaistS Offline
            SGaistS Offline
            SGaist
            Lifetime Qt Champion
            wrote on last edited by
            #12

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

            Interested in AI ? www.idiap.ch
            Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

            1 Reply Last reply
            0
            • Vivek_AV Offline
              Vivek_AV Offline
              Vivek_A
              wrote on last edited by Vivek_A
              #13

              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

              JonBJ 1 Reply Last reply
              0
              • Vivek_AV Vivek_A

                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

                JonBJ Offline
                JonBJ Offline
                JonB
                wrote on last edited by JonB
                #14

                @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_AV 1 Reply Last reply
                0
                • JonBJ JonB

                  @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_AV Offline
                  Vivek_AV Offline
                  Vivek_A
                  wrote on last edited by Vivek_A
                  #15

                  @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.
                  
                  
                  JonBJ 1 Reply Last reply
                  0
                  • Vivek_AV Vivek_A

                    @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.
                    
                    
                    JonBJ Offline
                    JonBJ Offline
                    JonB
                    wrote on last edited by
                    #16

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

                    1 Reply Last reply
                    1
                    • SGaistS Offline
                      SGaistS Offline
                      SGaist
                      Lifetime Qt Champion
                      wrote on last edited by
                      #17

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

                      Interested in AI ? www.idiap.ch
                      Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

                      Vivek_AV 1 Reply Last reply
                      1
                      • SGaistS SGaist

                        @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_AV Offline
                        Vivek_AV Offline
                        Vivek_A
                        wrote on last edited by
                        #18
                        This post is deleted!
                        1 Reply Last reply
                        0
                        • Vivek_AV Offline
                          Vivek_AV Offline
                          Vivek_A
                          wrote on last edited by
                          #19

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

                          1 Reply Last reply
                          0

                          • Login

                          • Login or register to search.
                          • First post
                            Last post
                          0
                          • Categories
                          • Recent
                          • Tags
                          • Popular
                          • Users
                          • Groups
                          • Search
                          • Get Qt Extensions
                          • Unsolved