Symbols loading from the target (via gdb/gdbserver) does not work #11949

Activity

1. browntarik

   added

   Language Service

   debugger

   help wantedCan be fixed in the public (open source) repo.Can be fixed in the public (open source) repo.

   on Feb 12, 2024
2. UR3IQO commented on Feb 14, 2024

   

   Oleg UR3IQO (UR3IQO)

   on Feb 14, 2024

   Last edited by UR3IQO

   Author

   More actions

   I looked at the GetInitializeCommands in DebuggedProcess.cs (MIEngine repo) and realized that Option 3 in the possible solutions was already implemented. So, I tried to use fully custom setup and launch gdb commands and it did the trick:

   {
      //NOTE: remote username, address, project directory and executable name are defined in the config file (.vscode/settings.json)
      "version": "0.2.0",
      "configurations": [
         {
            "name": "GDBserver debug",
            "type": "cppdbg",
            "request": "launch",
            "targetArchitecture": "arm",
            "useExtendedRemote": true,
            "program": "target:${config:remote.dir}/${config:remote.exec}",
            "miDebuggerServerAddress": "${config:remote.addr}:1234",
            "args": [],
            "cwd": "${workspaceRoot}",
            "environment": [],
            //"externalConsole": true,
            "sourceFileMap":{
               "/share/OGL" : "{$workspaceRoot}",
               "/share" : "D:\\src\\lib"
            },
            "customLaunchSetupCommands" : [
               { "text":"target extended-remote ${config:remote.addr}:1234", "ignoreFailure":false },
               { "text": "-file-exec-and-symbols target:${config:remote.dir}/${config:remote.exec}", "ignoreFailure":false },
               { "text": "set remote exec-file ${config:remote.dir}/${config:remote.exec}", "ignoreFailure":false },
               { "text":"set scheduler-locking step" }
            ],
            "windows": {
              "MIMode": "gdb",
              "miDebuggerPath": "C:\\gdb-arm-linux\\bin\\arm-linux-gnueabihf-gdb.exe",
              "preLaunchTask": "debug"
            },
            "logging": {
               "engineLogging": true,
               "trace": true
            }
       }
   }
   

   And the filtered log:

   1: (242) <-1001-gdb-set mi-async on
   1: (269) <-1002-interpreter-exec console "set pagination off"
   1: (274) <-1003-gdb-set auto-solib-add on
   1: (289) <-1004-gdb-set solib-search-path target:/share/OGL/build;
   1: (306) <-1005-interpreter-exec console "target extended-remote 192.168.122.233:1234"
   1: (382) <-1007-file-exec-and-symbols target:/share/OGL/build/main.elf
   1: (4407) <-1008-interpreter-exec console "set remote exec-file /share/OGL/build/main.elf"
   1: (4437) <-1010-interpreter-exec console "set scheduler-locking step"
   <--   C (setFunctionBreakpoints-3): {"command":"setFunctionBreakpoints","arguments":{"breakpoints":[]},"type":"request","seq":3}
   <--   C (setDataBreakpoints-4): {"command":"setDataBreakpoints","arguments":{"breakpoints":[]},"type":"request","seq":4}
   <--   C (setInstructionBreakpoints-5): {"command":"setInstructionBreakpoints","arguments":{"breakpoints":[]},"type":"request","seq":5}
   <--   C (setExceptionBreakpoints-6): {"command":"setExceptionBreakpoints","arguments":{"filters":[],"filterOptions":[]},"type":"request","seq":6}
   <--   C (configurationDone-7): {"command":"configurationDone","type":"request","seq":7}
   1: (4526) <-1011-exec-run
   
3. jfuentesa commented on Sep 30, 2024

   

   Javier Fuentes (jfuentesa)

   on Sep 30, 2024

   Last edited by jfuentesa

   More actions

   Is it possible to avoid sending the -file-exec-and-symbols command?
   I'm using the following syntax to start a gdbserver instance via stdin with a custom .gdbinit:
   "target remote | ssh HOST gdbserver - --attach PID"

   I don't want to debug the executable itself; instead, I want to debug a shared library. However, the trace shows the following error:

   --> E (output): {"type":"event","event":"output","body":{"category":"console","output":"1: (185489) <-1050-file-exec-and-symbols ......................../executable\n"},"seq":774}
   1: (185489) <-1050-file-exec-and-symbols ......................../executable
   --> E (output): {"type":"event","event":"output","body":{"category":"console","output":"1: (185519) ->1050^error,msg=\"\\\"......................../executable\\\": not in executable format: file format not recognized\"\n"},"seq":776}
   1: (185519) ->1050^error,msg="\"......................../executable\": not in executable format: file format not recognized"
   

   I have tested the options "launch" and "attach" but they don't work for one reason or another.
   "attach": It asks for a local PID.
   "launch": Try to run the program, which is already launched. It fails if the file does not exist (it only exists in the remote host).

   I need a way to override this behaviour.
   Thank you.