Dan Kegel schreef:
> On Jan 17, 2008 12:08 PM, Eric Pouech <[EMAIL PROTECTED]> wrote:
>
>>> http://bugs.winehq.org/show_bug.cgi?id=11211
>>>
>> you're likely running out of memory (just to be sure, if the test
>> segfaults, but winedbg correctly starts, it's likely the cause)
>>
>
>
On Jan 17, 2008 12:08 PM, Eric Pouech <[EMAIL PROTECTED]> wrote:
> > http://bugs.winehq.org/show_bug.cgi?id=11211
>
> you're likely running out of memory (just to be sure, if the test
> segfaults, but winedbg correctly starts, it's likely the cause)
It doesn't seem like I'm running out of memory.
Dan Kegel a écrit :
> I just tried to do another daily valgrind run, but
> it got blocked because it started up an infinite
> number of copies of winedbg. It seems that
> a crash in the imagelist test in GetDibBits
> triggered winedbg, and winedbg crashed trying
> to generate a backtrace, which of
I just tried to do another daily valgrind run, but
it got blocked because it started up an infinite
number of copies of winedbg. It seems that
a crash in the imagelist test in GetDibBits
triggered winedbg, and winedbg crashed trying
to generate a backtrace, which of course fired
up winedbg, which.
