Menu
▾
▴
1 Attachments
#551 Crash when quitting while connected to debugger and breaked
When I quit openMSX while connected the the debugger, and when openMSX is breaked, openMSX gives me one of the following four results:
- Nothing.
- Error message “Assertion failed: (ec == 0), fun”
- Error message “Assertion failed: (ec == 0), function unlock, file /Source”
- Crash, and error message “Assertion failed: (ec == 0), function unlock, file /SourceCache/libcxx/libcxx-120/src/mutex.cpp, line 45.”
The issue is quite intermittent, I would say 50% of the time I get no error at all, and the actual crash only happens 1% of the time. The attached crash report is from the fourth case.
My interpretation is that there is some kind of race condition between the assertion happening, and the program terminating before the error has been fully processed. I am using a current development build on Mac OS X 10.9, the debugger is built with Qt4.
Steps to reproduce:
- start openmsx
- start debugger
- connect debugger
- break debugger
- close openmsx
Discussion
If I put sleep(10) at the end of the CliConnection destructor I get a reliable crash reproduction.