Activity

1. WebFreak001 commented on Sep 27, 2021

   

   WebFreak001

   on Sep 27, 2021

   Owner

   More actions

   yes target: extended-remote can be used

   You can see the special case here:

   code-debug/src/backend/mi2/mi2.ts

   Line 215 in 5151db0

   if (target.startsWith("extended-remote")) {
2. maxgolov commented on Nov 12, 2021

   

   maxgolov

   on Nov 12, 2021

   More actions

   BTW: is it correct to set the "target": "extended-remote :12345" as seen in a different issue if I want to use extended-remote?

   What worked for me:

   • "remote": false
   • pid must be specified by autorun script.. Because you can't specify it for target that starts with extended-remote.

   Would it make sense to possibly add separate config options for launch.json , such as:

   • "extended-remote": true
   • "processId": 12345 or "pid": 12345

   ?

   This is the config that worked for me for extended-remote use-case:

   {
       "version": "0.2.0",
       "configurations": [
           {
               "type": "gdb",
               "request": "attach",
               "executable": "GdbSample",
               "cwd": "${workspaceFolder}/../../Install/Debug/Target-aarch64-xxxxx-linux-gnu/bin/",
               "name": "(gdb) Attach to Target",
               "target": "extended-remote 192.168.1.50:2345",
               "remote": false,
               "gdbpath": "C:/msys64/mingw64/bin/gdb-multiarch.exe",
               "printCalls": true,
               "valuesFormatting": "parseText",
               "showDevDebugOutput": true,
               "autorun": [
                   "attach 12345"
               ]
           }
       ]
   }
   
3. GitMensch commented on Apr 26, 2022

   

   GitMensch

   on Apr 26, 2022

   CollaboratorAuthor

   More actions

   Documentation was updated, inconsistencies handled with #330.
4. GitMensch

   closed this as completedon Apr 26, 2022