Hi all,

there have been occasional bad crashes of an application in whose development I'm involved in (Padre). With your generous help, I managed to build a debugging perl+wxWidgets+Wx combination and finally obtained a backtraces for such crashes. I always suspected a combination of ithreads with wx to be the culprit and unfortunately, it turns out I was right. It seems to happen only when a background thread is joined. Specifically during the resulting cleanup. I'm wildly speculating now: Maybe some of the Wx objects with underlying non-ithread-aware C++ implementation are being cloned on thread creation and dubiously freed on thread exit. Or maybe it's due to Thaw being called on a window that wasn't Freeze'd (see backtrace).

You can find an example backtrace with some additional debugging info here:

http://padre.perlide.org/attachment/ticket/287/backtrace

I'm unsure how to proceed with debugging these issues. I'm out of my depth, unfortunately, and would really appreciate any help.

Does anyone have any pointers on how I should go about finding the cause of this? Could you help if I provided more info? Right now, I'm able to conveniently reproduce that crash. I will try not to recompile or overwrite any part of the setup for a while in order to keep it that way. Please help.

Best regards,
Steffen

Reply via email to