QuickGDB source files not found

Sysprogs forums Forums VisualGDB QuickGDB source files not found

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #28099
    dde
    Participant

    Hi,

    we updated our VisualGDB from version 5.3.x to version 5.5.5.3595 and the QuickGDB debugging of a core dump doesn’t find our local source files anymore (Visual Studio 2013 and 2019 have the same behaviour here).
    Our build process generates the binary and .debug file which contains the debug information with the full path of the source files on our buildsystem.

    This path differs from the local build done in visual studio. One example:

    The path in the .debug file looks like this: C:\\worker\\vault\\build/sdk/common/os/debug.h
    The local path during QuickGDB debugging would be e.g. c:\\sources\\13r2\\apps\\events\\sdk\\common\\os\\debug.h

    The relative portion is sdk\\common\\os\\debug.h

    If I now create a directory C:\worker\vault\build and copy the project contents to this folder, QuickGDB finds the source files in this directory.
    I also tried the advanced GDB setting “Use relative source file paths instead of querying full path lists”, but this didn’t change anything.

    From your output I get e.g.:

    ^done,stack=[frame={level=”0″,addr=”0x0005a084″,func=”IInstanceLog::Log”,file=”sdk/common/os/debug.h”,fullname=”C:\\worker\\vault\\build/sdk/common/os/debug.h”,line=”94″},frame={level=”1″,addr=”0x0005c248″,func=”AppWebsocket::AppWebsocketMessageSend”,file=”sdk/common/lib-cpp/appwebsocket.cpp”,fullname=”C:\\worker\\vault\\build/sdk/common/lib-cpp/appwebsocket.cpp”,line=”421″},frame={level=”2″,addr=”0x00015398″,func=”EventsSession::DatabaseReadProgress”,file=”events/events.cpp”,fullname=”C:\\worker\\vault\\build/events/events.cpp”,line=”1032″},frame={level=”3″,addr=”0x0002684c”,func=”TaskReadEvent::DatabaseExecSQLResult”,file=”events/events_db.cpp”,fullname=”C:\\worker\\vault\\build/events/events_db.cpp”,line=”551″},frame={level=”4″,addr=”0x0006ca7c”,func=”_ZThn4_N18PostgreSQLDatabase15IoContextNotifyEbb”,file=”sdk/common/linux/postgresql/psql_database.cpp”,fullname=”C:\\worker\\vault\\build/sdk/common/linux/postgresql/psql_database.cpp”,line=”505″},frame={level=”5″,addr=”0x00042a28″,func=”IoMux::Run”,file=”sdk/common/linux/os-cpp/iomux.cpp”,fullname=”C:\\worker\\vault\\build/sdk/common/linux/os-cpp/iomux.cpp”,line=”530″},frame={level=”6″,addr=”0x0001496c”,func=”main”,file=”events-main.cpp”,fullname=”C:\\worker\\vault\\build/events-main.cpp”,line=”51″}]

    Do I have to change a configuration or can you make the old VisualGDB behaviour from version 5.3 working again?

    Greetings,
    Daniel

    #28104
    support
    Keymaster

    Hi,

    The path mappings for the Quick Debug presets can be edited by clicking the “edit source path mapping” button in the GDB Session window:

    Please double-check that the mappings shown there match your setup.

    If you are not sure, please attach a screenshot of the Edit Path Mapping window with your settings and we will help you understand what is going on.

    Attachments:
    You must be logged in to view attached files.
    #28107
    dde
    Participant

    Thanks, this worked! Strange though that it doesn’t automatically find the files anymore as in previous versions.

    Greetings,
    Daniel

    #28112
    support
    Keymaster

    Good to know it works. Despite redesigning the Quick Debug GUI, we haven’t changed the path mapping logic for a while, so the problem was likely caused by something else (e.g. you configured the path mappings in the older version, but them somehow reverted them).

    Either way, the mappings are stored in the .quickdebug files under %LOCALAPPDATA%\VisualGDB\QuickDebugPresets. Feel free to make a backup of them and use it as a comparison point in case of further problems.

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.