OK, Thanks for the info. I'll see what's at the link and whether I can
figure anything out from that, or else at least rebuild with gdb -g info
and go through the process that way to try and get more useful
information for you.
On Fri, 18 Jul 2014 08:09:40 +0900
Carsten Haitzler (The Rasterman) <[email protected]> wrote:
> On Thu, 17 Jul 2014 13:14:09 -0400 John Holland
> <[email protected]> said:
>
> > I also tried running enlightenmen_start with valgrind and I
> > captured the output with 2>&1 from the command line. These two are
> > in the attached files.
>
> so great... except you have no gdb debugging info so no files and
> line #'s... so all we can say is "somewhere in that 130,000 lines of
> code or so are some uninitialized vars or invalid reads". can't do
> anything with that. last time i ran e under valgrind, i didn't see
> anything like this. :( so something unique about your situation is
> causing this. :(
>
> https://phab.enlightenment.org/w/debugging/
>
--
John Holland
[email protected]
gpg public key ID 0x9551CF2D
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
enlightenment-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-users
