Hi Raster, On Wed, 17 April 2013 Carsten Haitzler (The Rasterman) <ras...@rasterman.com> wrote: > > Full valgrind log attached to the bug. > > that's a little more useful. it gives me an actual address. the address looks > sane - ie it's writing to and invalid memory region. it'd be goot to get a > backtrace there: valgrind --db-attach=yes ... that will ask to attach gdb per > complaint - if you say yes, you can get a backtrace (bt command) and print > variables/values.
Attached is a combination of valgrind output, gdb backtrace (only the innermost functions) as well as a detailed view of src, dst and dc. Hope this is useful information. Bruno
enlightenment1.gdb
Description: Binary data
------------------------------------------------------------------------------ Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
