Cedric BAIL, il 06/08/2013 08:20, ha scritto:
> All your backtrace point to either malloc or free. This is a clear
> sign of memory corruption. It also means that those backtrace are
> sadly useless. You need to run enlightenment with valgrind to tell us
> what is going on.
The problem is that the only constant is the high CPU usage, that
segfault happened only once until now and I can't say when it will
happen again.
I guess in this case a valgrind log, like the one I already sent, is
just as useless as the backtrace :(
> You should be able to get the problem under Xephyr
> to (at least try there first, if it doesn't show anything, then you
> are good for a slow motion session).
Do you mean that I could use valgrind under Xephyr to track the memory
usage of an already running E when it segs, just as I would attaching
gdb to it?
Currently when I need to use valgrind I invoke it via xinit.
--
Massimo Maiurana GPG keyID #7044D601
La fede e' credere in cio' che sai non essere vero
[Mark Twain]
------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent
caught up. So what steps can you take to put your SQL databases under
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
