On Fri, 2 Apr 2004 11:17:30 +0200 (EET), you wrote: > On Thu, 1 Apr 2004, Rein Klazes wrote: > > > > i am asking not exactly for that. i would like to find out what call > > > sequence was made in the wine thread that caused crash at point of making > > > > Alternatively you might try to run winedbg (seems that you already found > > that) or run the whole thing under gdb. > > eghm. i think i didn't find it. winedbg crashes in similar way as wine and > i am only starting to learn how to write expressions for winedbg's > conditions. If that gets to hard, you can put some C code in the function where you want to break: if( <condition> ) DebugBreak(); > gdb is a unexplored way too for me. OK. > > It might be a good thing to report this on the wine developer list. It > > i would but only after compiling cvs-version. > > > looks clearly as a kernel fault, but somebody might still be interested > > to fix this within wine. > > and OTOH: how do you think, shouldn't i report this to kernel devs? Of course, I assume that you want to investigate first (and perhaps test a recent kernel version). Rein. -- Rein Klazes rklazes@xxxxxxxxx _______________________________________________ wine-users mailing list wine-users@xxxxxxxxxx http://www.winehq.org/mailman/listinfo/wine-users
