How to use this extension with coredumps [missing in README]?

So far I’ve only started the application, then used the debugging console or autorun to load a core file. But there is likely a better way, isn’t there?

Thinking about that it would be likely useful to have an extra launch type for that which has no pause/run/step active (if this is actually possible with the dap).

Additional: On systems with installed systemd-coredump all created coredumps are taken into its db and the last one can always be inspected with gdb using coredumpclt debug (you can filter for example with pid or executable name, too). It would be really nice to start this instead of GDB - but I have no clue if this would work, I guess via its --debuger (default is gdb - we’d just set the gdbpath there) and via --debugger-arguments= (to pass the collected startup commands). That would be useful both locally and for ssh-remote. Maybe a new type “core” with an optional boolean argument coredumpclt?

[brownts]

I see, that’s microsoft/vscode#6209, one needs an explicit problem matcher, that’s… special. It still doesn’t work for me using this exact same definition, the launch does not start. It does work when manually starting that process, then creating the launch (in this case it is ideal to drop that “once”, of course.

Yeah, getting the matcher correct is a pain, but I remember running across that in the past and had this in my back pocket from some previous launcher I had cobbled together.

Not sure why it’s not working for you. With that setup, at least on Linux, I’m not having any problem launching gdbserver.

Note: I don’t see any interaction to show local variables - should there be some? Did I somewhere possibly dropped that with a setting? [note: hovering over variables leads to the data-evaluate-expression call and the returning output is also resolved nicely in the gui - the variable pane “Local” is just empty.

Not quite sure exactly what you’re seeing, but I do see many local variables shown. I do see that some seem to have problems (which should be investigated), but others are displayed fine. Here are a couple snapshots from my hello_world example. I just ran this and when it’s in the sleep loop, I ran “gcore” on it to generate a core file. Then loaded it as previously described.

[GitMensch]

I’m using the last release, as most people 😃 0.26.0 - that fix is not included there.