[ I assumed the BTS would send a Cc to the gnucash maintainer due to the affects header, but that probably wasn't the case. Sorry, Sébastien. ]
On Wed, Oct 08, 2014 at 08:25:05PM +0200, Matthias Klose wrote: > are there any suspicious compiler warnings? maybe fix these first. -Werror -Wall passes with flying colors. > please try to build gnucash with -O1 or -O0 and see if it works. If yes, build > half of the object files with -O2 (the default) and with -O0. Then try to > reduce the files built with -O0. Once you have identified one file, continue > using the optimize attribute to lower the optimization level for a function > until you have identified the misbuilt function. Thanks! That was exactly what I needed to track it down. As inferred by the backtrace from my previous email, the culprit is indeed gsslrtma_populate_tree_store(); optimizing it with -O1 or -O2 triggers the segfault. I tried to dig a little deeper, but to no avail. The collect_values argument to value_collect_string() on frame 2 is "bad", but inbetween that and gsslrtma_populate_tree_store() are three frames full of optimized-out variables, opaque varargs, and internal GTK/GNOME macros. That's beyond my league. Sébastien, I think I'll pass the baton to you now. :) Let me know if there's anything I can do to help. -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141009150030.ga16...@fabul.fbriere.net