Johannes Sixt

I don't understand what `info target` has to do with the original problem that GDB could not be started in the first place and that the Run command is disabled....

When GDB was not started, *nothing* can work. So, please explain why you have a dump of GDB commands at all. Is it wrong that GDB did not run? Did...

> I don't know why kdbg reports that gdb failed to start though. The message happens when `KDebugger::debugProgram` returns `false`. There are two `return false` statements in the function. Please...

> * c(ontinue). One I use all the time. It looks like the `Run` command becomes `Continue` once the debuggee is started but that's an ambiguous implementation that clashes with...

Can I have a look at the model file? You can send it to my github address if you do not want to publish the file. Also, it would be...

Here is a reproduction recipe. Write this in a file `fp-inaccuracy.ldr`: ``` 1 0 -100 20 0 0 1 0 0 0 1 1 0 0 2340.dat 1 36 -86...

You do not describe sufficiently what is broken and what must be fixed. A screenshot can help. A shot in the dark: Switch Z-snapping to 1/2 stud.

Works for me as expected: the accelerators are invisible and become visible as underlined letters only when I press Alt. This happens both in English and localized versions.

I have no idea what is going on. Can you try to move away `.config/kdbgrc` so that you start with pristine settings? Do you have an old `kdbgui.rc` somewhere in...

> * That you only see accelerators when pressing Alt is because you're on Windows while I see them all the time because I'm on Linux, as I learned at...