|
From: songbird <son...@an...> - 2012-08-06 12:24:24
|
Julian Seward wrote: > On Wednesday, August 01, 2012, songbird wrote: all fixed (executive summary, see end of msg :) ). >> hello, and thanks for such a fun group of tools >> to work with, :) > > Sounds like you need more memory. wish i had a whole new machine. :) for the program i'm working on 512Mb is plenty. usually it compiles to less than 500Kb even with all debugging symbols/information included. >> --00:00:00:00.000 27357-- --read-var-info=yes > > This is possibly the cause of the problem. Remove it. > > Removing --track-origins=yes might also help a bit. thanks for the reply, i made sure to exit all extra windows and programs when i was running valgrind and it wasn't using swap space or doing heavy disk io. i also added a nice call to the front to make it run at the minimum priority, which made the mouse movements happen, but very jittery. yet when i clicked any other window or program it still would not switch. in the meantime a new version of the linux kernel was uploaded to Debian experimental -- I gave it a try and now mouse works, windows click and valgrind runs all together. songbird |