Mario A. Cozzuol wrote: > However I am a bit confuse. In the link you sent it seems that the problem > is with dplayx DLL, but after run the debug option in my case no complains > with dplayx DLL appears, but many with ntdll. No, read the top of the page - it explains how to debug an exception loop which causes a stack overflow. That's exactly what you're seeing. > So, I am afraid that the direcction in this page cannot apply to my > problem. Or I am wrong? Yeah :-).. As per the article linked to, you need to enable +seh debugging along with any other debugging channels that you think are related, and then backtrace the debug log for the first seh:EXC_RtlRaiseException, and see what comes "immediately" before that. (If you're curious and want to know why it goes into an exception instead of just dying at the first exception, you'll have to ask on wine-devel. I have no clue.) _______________________________________________ wine-users mailing list wine-users@xxxxxxxxxx http://www.winehq.org/mailman/listinfo/wine-users
