Quote:
Originally Posted by Johan K
I (dom3 developer) am reading this forum quite often, so posting here works fine. But the backtrace was useless though 
If you get a backtrace with less ?? then I would be glad to see it and I might even figure out what went wrong. Running without sound (-d) might help too so you don't get a backtrace of the sound thread by mistake. |
Good, I could provide you with some additional infos:
- That error was most propably newly introduced with 3.23. I played a lot with earlier versions and never had that before.
- I absolutely never play with game sound (I have my own taste :-))
- The ?? lines of the backtrace are not completely useless: the 400000x address range is in the dom3 app, not in any dynamic library. So the nanosleep_nocancel() was directly called by dom3
- the 2 last -d debug log lines before the freeze:
ustatbox unr4624 sel(nil)
guiarea 14 x 175.000000 y 500.869507 450.000000x32.670013 alpha 0.200000