On 25/07/06 19:14:46, Sascha Heid wrote:
I don't think the ?? stack frames are because of missing debug symbols. It looks like stack corruption, so the backtrace is of no use as the problem occurred some time before the segfault.
I'm thinking the segfault may only occur because of something changed in GTK 2.10.0 or the corresponding GLib (Sascha: what version of GLib?)
The output of Valgrind may help diagnosing the problem when the corruption first occurs: valgrind --tool=addrcheck --leak-check=no /path/to/geany
I haven't tested Geany with GTK 2.10.0 yet. It's difficult to say whether the problem is Geany or GTK 2.10.0 or the Gentoo system...
I was unable to get more debugging symbols yet (i used USE="debug" and removed fomit-frame-pointer from my flags).
OK, you might get a different backtrace now using a build without -fomit-frame-pointer. If so please post it back to the list - this could be why there were ?? entries.
For debug, the flag is -g, but the Geany build system normally enables this already. Also for debugging it's best not to optimize higher than -O2.
I wanted to try valgrind but couldn't figure out where to get the addrcheck tool, so i used memcheck, maybe its of some use: [...]
Thanks, memcheck is just a heavier version of addrcheck.
Unfortunately Valgrind didn't reveal anything in Geany directly causing a problem, so it could be some incompatibility or a bug in GTK 2.10.0/GLib 2.12.1.
Regards, Nick