On Sun, 9 Oct 2005, Mike McCormack wrote:
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
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
need to.
If you want
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.
Randall Walls
Mike McCormack wrote:
Randall Walls wrote:
Mostly I'm just curious if this is an issue with Wine's
Randall Walls wrote:
Mostly I'm just curious if this is an issue with Wine's heap
implementation, or if it is more likely just a poorly built application
that I should give up on.
No and no. It's likely to be an issue with some other function in Wine
that is corrupting the heap. The best w
Greetings,
I've been (unsuccessfully) attempting to run a children's program
through wine for some time. I've been trying successive releases since
about may, without luck. The program appears to be extremely simple,
just some painting apps for toddlers, but each run fails with what looks
like
