How to debug destroyed call stack?
Cenedese at indel.ch
Wed Nov 6 06:02:40 CST 2002
I have a program that crashes at startup. The backtrace shows only one
entry (and obviously a wrong one). What's the best way to find this error?
Is it possible that my program can write into wine's memory? It runs fine
in Windows so I don't think that there are many flaws in it (though still
of course :) It's a multithreaded ocx so it's not that easy to debug.
It happens in various versions from cvs.
Thanks for any hints.
More information about the wine-devel