It does not matter which CPU type is specified (none or -mstm8, didn't test more) or which filename is given on startup - cdb or ihx.
The only thing that does at least something is a simple "break" without parameters or "break" with names that don't exist:
Sorry, your question got lost in my inbox. No, the problem is still there for me with both, the official package for 4.0.0 and 4.1.0 (build #12072). For 4.0.0 I used the official binary build, for 4.1.0 I compiled the source myself, because the binary package does not work with the libraries on my system (Mint 20.2, based on Ubuntu 20.04).
I removed all other versions of sdcc out of the path to make sure that I don't versions here.
I tried strace, but it does not show any trace of an attempt to execute the simulator binary. Is this right? No fork, no open, no exec. Here are the last few lines. The prompt is written, my input is read and then - nothing.
sdcdb always crashes with a segfault when I want to set a breakpoint:
It does not matter which CPU type is specified (none or -mstm8, didn't test more) or which filename is given on startup - cdb or ihx.
The only thing that does at least something is a simple "break" without parameters or "break" with names that don't exist:
Am I getting it totally wrong or is sdcdb really not useable? It would be super useful.
I tried this with an older snapshot build and with the 4.0.0 release, compiled on my system from the official 4.0.0 source archive.
Hi, Michael. Have you fixed the segmentation fault?
Sorry, your question got lost in my inbox. No, the problem is still there for me with both, the official package for 4.0.0 and 4.1.0 (build #12072). For 4.0.0 I used the official binary build, for 4.1.0 I compiled the source myself, because the binary package does not work with the libraries on my system (Mint 20.2, based on Ubuntu 20.04).
I removed all other versions of sdcc out of the path to make sure that I don't versions here.
I tried strace, but it does not show any trace of an attempt to execute the simulator binary. Is this right? No fork, no open, no exec. Here are the last few lines. The prompt is written, my input is read and then - nothing.
The full trace for a stock v4.0.0 is attached to this message.