Need advice on which native dlls to try

Duane Clark dclark at akamail.com
Tue Feb 6 12:33:52 CST 2001


gerard patel wrote:
> 
> On Mon, 05 Feb 2001 22:19:12 -0800, Duane Clark <dclark at akamail.com>
> wrote:
> 
> <snip>
> >0011: sel=008f base=40110e00 limit=00000fff 32-bit rw-
> >Backtrace:
> >=>0 0x407816fd (QUEUE_GetQueueTask+0x29(hQueue=0x467) [queue.c:1299])
> >(ebp=40586050)
> >  1 0x4078cd62 (EnumTaskWindows16+0x66(hTask=0x1bf, func=0x307859c0,
> >lParam=0x138) [win.c:2913]) (ebp=40586074)
> >  2 0x4078cde8 (EnumThreadWindows+0x2c(id=0x8777348, func=0x307859c0,
> >lParam=0x138) [win.c:2937]) (ebp=40586098)
> >  3 0x307859a3 (MSO97V.DLL.WindowFromDlg+0x791) (ebp=00000138)
> >
> >0x407816fd (QUEUE_GetQueueTask+0x29 [queue.c:1299]): movw
> >0xc(%eax),%si
> >1300            QUEUE_Unlock( queue );
> >Wine-dbg>
> 
> I think that this crash is because Wine does not destroy
> the windows of a thread when TerminateThread is
> called.
> 
> Gerard

Okay, I really don't know what that means. But I would just say that in
every case, I get these when an attempt is made to create a dialog, not
destroy them, though something else may be being destroyed in the
process. The only thing that I see being destroyed is the drop down
menu, and it is successfully destroyed and the background repainted
before the crash.

By the way, this particular crash is repeatable. While the amount of
playing around to generate it is random, the crash backtrace is
generally exactly the same.

Duane




More information about the wine-users mailing list