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... was bad. Some of the logs are at http://bugs.winehq.org/show_bug.cgi?id=11211
This seems to be very recent breakage, either today or yesterday. - Dan
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 course fired up winedbg, which... was bad. Some of the logs are at http://bugs.winehq.org/show_bug.cgi?id=11211
This seems to be very recent breakage, either today or yesterday.
- Dan
you're likely running out of memory (just to be sure, if the test segfaults, but winedbg correctly starts, it's likely the cause) A+
On Jan 17, 2008 12:08 PM, Eric Pouech eric.pouech@orange.fr wrote:
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. winedbg does not correctly start. free shows lots of free swap space.
Amusingly, this shows up now on one of my machines when I run Photoshop CS2 tryout. File / Browse crashes, which will bring up winedbg, which crashes, which brings up winedbg, which crashes,... you have to do wineserver -k quick or you'll have zillions of winedbg's all waiting to be debugged.
Dan Kegel schreef:
On Jan 17, 2008 12:08 PM, Eric Pouech eric.pouech@orange.fr wrote:
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. winedbg does not correctly start. free shows lots of free swap space.
Amusingly, this shows up now on one of my machines when I run Photoshop CS2 tryout. File / Browse crashes, which will bring up winedbg, which crashes, which brings up winedbg, which crashes,... you have to do wineserver -k quick or you'll have zillions of winedbg's all waiting to be debugged.
A single application can only use 3 gb of memory, it doesn't have to be actual memory, it can be 'virtual' as well. This means it's reserved, but it doesn't necessarily have to be used. You can see this in top under the virt column.
-
Dan Kegel -
Eric Pouech -
Maarten Lankhorst