I see the same in the GuiViewPrivate constructor in your valgrind log. Could it be that something has not been initialized yet at this point ? We're able to draw strings, after all...
That's puzzling. JMarc On 8 février 2014 21:28:07 UTC+01:00, Stephan Witt <st.w...@gmx.net> wrote: >Good idea, I thought of it already but didn't expect it's available on >Mac, but it is. > >It points to the same code area and tells something about the bad >memory area accessed. >At line 193 of the attached log file is an invalid read with a matching >call stack listed. >But I'm not sure if it's the real cause, what memcheck says.
