SchodMC

Forum Replies Created

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • SchodMC
    Participant

    (Sorry for posting the other message to the wrong thread)

    I just installed the latest beta Version (5,6m Beta 3) and it didn’t help. Here’s the screenshot.

     

    //EDIT: I also tried a repair installation – now change. I even don’t need to enter a path mapping. Just open the dialog for the mapping from the GDB Session pane and than click on ok (without entering or changeing nothing) brings up the error message.

    • This reply was modified 2 years, 10 months ago by SchodMC.
    Attachments:
    You must be logged in to view attached files.
    SchodMC
    Participant

    Wow, I`m impressed. That was fast!!! I tried it out and it works like a charm. Thank you very much!!!

    SchodMC
    Participant

    I have only the following Extensions installed:

    • Test Adapter for Google Test
    • Visual Studio IntellliCode (disabled)
    • Live Share
    • VisualGDB
    • SourceGear Vault
    • Test Adapter for Boost.Test

    Beside Vault and VisualGDB all are default from VisualStudio. I disabled at least Visual Studio IntelliCode, but that doesn’t change anything.

    I also made a mingw test project and enabled “Advanced Clang IntelliSense” in the Visual GDB Project Settings, same problem. Maybe you can reproduce it (I added the CPP file to the post). I set a breakpoint at line 15, run the code and when the app stops at that line, I put the mouse over “showIt”, and nothing happens. And as described above, it’s the same problem when pressing shift+f9 – QuickWatch trys to evaluate “->showIt”. Move with the mouse over this, unfold it and search for “showIt” works, but is not that comfortable (especially with complex classes).

     

    P.S.: Using the default IntelliSense works, too. But the one VisualGDB offers is much better, so I want to use that.

    Attachments:
    You must be logged in to view attached files.
    in reply to: Debugging only with gdbserver #7310
    SchodMC
    Participant

    Well, I look to the output and realized, that this command won’t be executed. Setting it manually won’t work (got an file not found error). The configuraion of Visual GDB tells me, that it wants to use GDBServer. But I also think that I have a completley missconfigurated visuagdbproject file.

    What I whant is the following (as told in an other thread):

    • Use an existing project
    • Add a new configuration
    • Copy a visual gdb project file to my source and set it as output file in the Visual Studio settings, to acticiate VisualGDB.
    • Then I want to tell VisualGDB to execute my make command line to compile the project like already configured in Visual Studio
    • After that, VisualGDB has to copy the file to my remote machine to an directory I want
    • And than, VisualGDB should start gdb on the remote machine (using SSH) and debug the previously copied application without sending a copy of the source file, just like Quick Debug do. That said, Visual GDB should simply start a debugging session like it will work when I call the Quick Debug menu command.

    I don’t know why, but I won’t get it work. Quick Debug always works like a charme (compiling with my own tool chain (with has no cross GDB or cross GDBSERVER on windows), copying the file manually to my remote machien and start quick debug – works without a problem. Even if I let VisualGDB compile the file and copy it to my remote machien I can use Quick Debug without a problem. Visual GDB always finds the sources, uses SSH, shows me the output of my app, shows any local variable, etc. Work, like it should work.

    And exactly that I whant to do with an VisualGDB project file, so that I simply have to press F5 and everything is fine. And this with an existing project using a seperate configuration, so that other developers in my company only have to change the configuration in Visual Studio to continue work on that project like the always did, without the need of VisualGDB. We need that, because the build chain we are using will be called by a chrone job for our release builds, that also includes other types of projects. So I don’t have the luxus to change all projects to build like a new Visual GDB will do with it own tools chains.

    Please, could you help me to make that work? Because the fact that Quick Debug works like a charme shows me, that there has to be a way to work like this, simply by addign a visual gdb project file to my existing projects and activating it with a new configuration.

    Have a nice day

    Marc

    in reply to: VisualGDB with own build chain (make) #7287
    SchodMC
    Participant

    That works, thanks! 🙂 Now I have some other problems, but I will open other threads for it.

    in reply to: VisualGDB with own build chain (make) #7268
    SchodMC
    Participant

    Thanks for that information.

    But how can I make this with an already existing projekt (I already have everything: solution, project files, …). And this will be used by other developers that don’t have Visual GDB. :-/ What I need is to add some kind of configuration (or something like that) to my existing project, so that I will be able to use VisualGDB, while can continue to work without having VisualGDB installed.

     

    EDIT: When I try to add an Visual GDB Configuration manually, and I want ot cross compile, I have to select gdb.exe. But I just want that this Visual GDB Linux Configuration to call make and make the debugging procedure like quick debug make it. Is that possible?

    • This reply was modified 8 years, 5 months ago by SchodMC.
Viewing 6 posts - 1 through 6 (of 6 total)