|
From: Randall H. <lis...@ch...> - 2003-11-14 14:35:17
|
Jeremy Fitzhardinge: |On Tue, 2003-11-11 at 14:43, Randall Hopper wrote: |> Switching to KDE, --assume-2.4=yes gets me past that error, but then after |> some minutes valgrinding this app locks my machine hard; it's completely |> net dead and console dead. Don't see this with my 9/23 CVS snapshot. |> |> BTW, this is on SuSE 8.2. | |Ah, well, that's what we like to call a kernel bug. No matter what junk |Valgrind does, it shouldn't lock the kernel like that. | |Obviously it could be a Valgrind bug too, and we'd like to fix it, but I |wonder if there's a kernel update from SuSE, or perhaps you could try |just installing a stock 2.4 kernel? SuSE does have a kernel update, which I'm running. I can try a stock kernel later. |What does your app do? Does it have lots of threads? Do lots of |syscalls? Does it seem to be all working fine, and then it all falls |over, or does it gradually collapse? Any oopses or other kernel |messages on the console? The app has about 10 threads, one using OpenGL. Probably a fair. It seems to be working fine, albeit slowly compared to previous valgrind snaps and eventually the GUI just freezes and it quits responding to events. Same with keyboard, net, etc. xosview doesn't suggest that we're running out of memory -- I have a Gig on this box (though this valgrind snap was consuming more than previous snaps) . No other clues that I'm aware of. The ATI OpenGL drivers do use SSE which valgrind doesn't quite deal with right yet, but I was only debugging app startup which used to work fine with older snaps. Sorry I can't provide more useful input. I'm not really sure what to look for. Randall |