06-02-2013, 08:13 AM
Hmm, what I really want to see is a stack trace. Those are just recently executed syscalls, it could be not in atrac at all... it looks like it's crashing in libc, so probably a memcpy() from a bad address.
When it crashes to the debugger, is there anywhere you can get a stack trace?
It should look something like the screenshot here:
http://stackoverflow.com/questions/76243...rror-shown
-[Unknown]
When it crashes to the debugger, is there anywhere you can get a stack trace?
It should look something like the screenshot here:
http://stackoverflow.com/questions/76243...rror-shown
-[Unknown]