Debugger unhappiness blocking valgrind runs
maarten at codeweavers.com
Fri Jan 18 05:51:07 CST 2008
Dan Kegel schreef:
> On Jan 17, 2008 12:08 PM, Eric Pouech <eric.pouech at 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.
More information about the wine-devel