dmott

Forum Replies Created

Viewing 12 posts - 1 through 12 (of 12 total)
  • Author
    Posts
  • in reply to: Working directory vs Binary directory #24790

    dmott
    Participant

    Thanks for the clarification.

    Working directory…does not have effect…with the Advanced CMake Project Subsystem.

    Suggestion to disable it in this mode to avoid confusion.

     

    Also WRT the clean option, thanks for the clarification.

    Suggestion to default to a ‘smart’ clean option.

    if (${CMAKE_BINARY_DIR} EQUALS ${CMAKE_HOME_DIRECTORY})

    cmake –build . –target clean

    else()

    rm -rf *

    endif()

    • This reply was modified 7 months, 3 weeks ago by  dmott.
    in reply to: cmake project with google test #20292

    dmott
    Participant

    Thanks, I updated the example here. This is also what I’m seeing in the production build. The test discovery phase seems to only scan the first GTest binary though multiple are being created.

    Please advise

    in reply to: cmake project with google test #20225

    dmott
    Participant

    Here’s a project with a similar symptom.  This one is showing one of the tests in the test explorer but another isn’t discovered.

    in reply to: cmake project with google test #20134

    dmott
    Participant

    I was able to run one test today but as it happens I performed a bit of work on our build system today and it’s stopped working. All the test build targets show up in the solution explorer, everything compiles and executing ‘make test’ runs the gtest binaries.

    At the end of the build I see this in the output panel:

    VisualGDB: Warning: _ZN7testing8internal12UnitTestImpl11RunAllTestsEv not found in the output file. Please ensure that your test framework is initialized properly.

    The Tests panel shows this:

    [2/16/2018 5:10:48 PM Informational] —— Discover test started ——
    [2/16/2018 5:10:49 PM Informational] Loading …xxx.vgdbtestcontainer…
    [2/16/2018 5:10:49 PM Informational] Downloading ….xxx_tests to discover tests…

    [2/16/2018 5:10:51 PM Informational] Test container loaded (lookup: 2 msec, fetch: 932 msec, symbol list: 49 msec)

    [2/16/2018 5:10:51 PM Error] Value cannot be null.
    Parameter name: filePath
    [2/16/2018 5:10:51 PM Informational] ========== Discover test finished: 3 found (0:00:02.2780564) ==========

     

    It also seems to drop and reconnect the ssh session.

     

    Please advise

    in reply to: cmake project with google test #20115

    dmott
    Participant

    all set, what should I look at?

    in reply to: cmake project with google test #20098

    dmott
    Participant

    I went through the walk-through here: https://visualgdb.com/tutorials/tests/googletest/. The sample project compiles but the tests dont appear in the test explorer window.

    Please advise

     

    in reply to: cmake project with google test #20097

    dmott
    Participant

    Interesting. Now after the successful build a popup says ‘Your version of VisualGDB does not support linux’ Its a large project with a lot of targets, which project types support integrated gtest?

     

    in reply to: cmake project with google test #20083

    dmott
    Participant

    TestFramework.cmake:

     

     

    in reply to: Target machine hangs on single step #10036

    dmott
    Participant

    I can appreciate the complications with a process debugging itself but it seems the claims of the product’s capabilities are a bit disingenuous. Has the JTAG debugging on x86 been tested? If so, what setup was used?

    in reply to: Target machine hangs on single step #10009

    dmott
    Participant

    Thanks for the info. Do you have a list of supported machines with JTAGs or a list of machines that are known to work and same with JTAG interfaces?

    in reply to: LIBSSH2_ERROR_SOCKET_SEND during deploy #7522

    dmott
    Participant

    I’m using DropBear SSH server on the target and OpenSSH on the build machine.

    in reply to: Kernel debugging in emulators #6296

    dmott
    Participant

    Hi Bazis, thanks for the reply. My kernel is custom (non-linux) so need some power tools to debug ACPI, PCI and processor tables (GDT/IDT), etc.  Short of going with ICE or JTAG, Bochs is the best thing I’ve found so far. It has a built in GDB-ish debugger but also includes a native GDB stub. If you have a go at it with any success please let me know. My thought was to create a VSIX with a debug engine and some tool windows to inspect processor tables, etc because Bochs has nearly everything already written on the back end for it but the VSIX SDK makes me ill. Debugging a kernel as the processor sees it without injecting code is a challenge with few solutions at present.

Viewing 12 posts - 1 through 12 (of 12 total)