Sebastian Macke

Ok, will do it

I have recompiled the toolchain. It looks like I have more to do than just compile gdb. I have to Implement former unused and new CPU instructions.

No, that's fine. The "safe"-CPU is already working with the new instructions.

Gdb compiles and runs, but crashes with a segmentation fault as soon as I try to debug something. Also there seems to be another bug somewhere which leads to glitches...

This is my test environment: https://jor1k.com/jor1k/ Type "help" in the terminal and you see what I mean. The only difference here is, that I use the newest musl-lib and compiled...

It is not a problem of musl. So it must be either in the new toolchain or in the emulation

Ok, I was able to compile the new kernel with all patches I need. Also I guess, that the problem with the terminal is a missing feature in my terminal...

I have considered it, but I think the main reason was, that such a terminal doesn't support streaming. E. g. it has to handle an incomplete utf-8 byte stream.

Anyhow, the problem with the terminal is solved. Now, after two weeks, I can finally try to find the problem in gdb.

I compiled everything without patches and for or1ksim. So nothing jor1k related. The same problems occur when you start gdb. Guess it is easier to ask @stffrdhrn. The problems are...