mike at codeweavers.com
Sat Oct 8 21:33:34 CDT 2005
Randall Walls wrote:
> Trace is 138 MB and then some. Should I attach the entire trace, or can
> I pare it down a bit to only the important stuff? I'm not sure exactly
> what to look for in this scenario.
You can post the trace on a website and add a link to bugzilla if you
If you want to try to debug the problem yourself, search backwards in
the trace from the point of the crash and look for HeapAlloc and
HeapFree calls that are using a similar address, give or take 0x100 hex.
To do that, I use "less" and the first 6 digits in the address like:
You can also try a +relay,+heap trace. That might give you a heap error
a little earlier and help narrow down the problem.
More information about the wine-devel