On Tue, 06 Aug 2013 13:40:59 +0200 Massimo Maiurana <maiur...@gmail.com> said:
> 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. well several things. 1. you could use oprofile to profile your os as a whole and find out where cpu time is being spent when e is consuming cpu. run it for a long enough period (a few minutes or maybe an hour) and we'll get enough samples to get a better idea of whats going on. you'll want gdb debugging symbols on in efl and e. 2. you could use valgrind with callgrind as the tool (--tool=callgrind - see manual page) to get very detailed call graphs and to find out what is calling what and how often - like oprofile but much more detailed. 3. yes - valgrind could also tell you memory usage (--tool=massif) and you can monitor/profile it. 4. valgrind could help maybe track down that segv... (standard default --tool=memcheck). :) > -- > > 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 > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) ras...@rasterman.com ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. 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
