Another crash, output from gdb (bt not possible) gdb) run^M(gdb) run^M(gdb) run Starting program: /usr/local/bin/gnucash [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". [New Thread 0x7fffe21e8700 (LWP 6203)] [New Thread 0x7fffe19e7700 (LWP 6204)] [New Thread 0x7fffda733700 (LWP 6205)] [New Thread 0x7fffb684b700 (LWP 6207)] [Thread 0x7fffb684b700 (LWP 6207) exited] [New Thread 0x7fffb684b700 (LWP 6208)] [New Thread 0x7fffabdfa700 (LWP 6397)] [Thread 0x7fffabdfa700 (LWP 6397) exited] [New Thread 0x7fffabdfa700 (LWP 6440)] [Thread 0x7fffabdfa700 (LWP 6440) exited] [New Thread 0x7fffabdfa700 (LWP 6465)] [New Thread 0x7fffab4f7700 (LWP 6466)] [New Thread 0x7fffa9f98700 (LWP 6469)] [New Thread 0x7fffa9797700 (LWP 6470)] [New Thread 0x7fffa8f96700 (LWP 6471)] [New Thread 0x7fff5b372700 (LWP 6489)] [New Thread 0x7fff5ab71700 (LWP 6490)] [New Thread 0x7fff5a370700 (LWP 6491)] [New Thread 0x7fff59b6f700 (LWP 6492)] [New Thread 0x7fff5936e700 (LWP 6493)] [New Thread 0x7fff58b6d700 (LWP 6494)] [New Thread 0x7fff43fff700 (LWP 6495)] [New Thread 0x7fff3b7f5700 (LWP 6496)] [Thread 0x7fff3b7f5700 (LWP 6496) exited] [New Thread 0x7fff3b7f5700 (LWP 6562)] [Thread 0x7fff3b7f5700 (LWP 6562) exited] [New Thread 0x7fff3b7f5700 (LWP 6617)] [Thread 0x7fff3b7f5700 (LWP 6617) exited] [New Thread 0x7fff3b7f5700 (LWP 6657)] [Thread 0x7fff3b7f5700 (LWP 6657) exited]
Program received signal SIGSEGV, Segmentation fault. 0x00007fffe28e84dc in Oxygen::MenuStateData::menuItemIsActive(_GtkWidget*) const () from /usr/lib64/gtk-2.0/2.10.0/engines/liboxygen-gtk.so (gdb) (gdb) Error detected on fd 0 error detected on stdin A debugging session is active. Inferior 1 [process 6200] will be killed. Quit anyway? (y or n) output.log lines 27-78/78 On Mon, Mar 3, 2014 at 4:31 PM, Ted Creedon <tcree...@easystreet.net> wrote: > Noticed this on startup: > > Missing separate debuginfo for /usr/lib64/libgobject-2.0.so.0 > Try: zypper install -C > "debuginfo(build-id)=a3f8edc19f47fd2290dbbf3d05670ed13ba6a93c" > Traceback (most recent call last): > File "/usr/share/gdb/auto-load/usr/lib64/ > libgobject-2.0.so.0.3800.2-gdb.py", line 9, in <module> > from gobject import register > File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module> > import gdb.backtrace > ImportError: No module named backtrace > Missing separate debuginfo for /usr/lib64/libglib-2.0.so.0 > T > > > On Mon, Mar 3, 2014 at 4:12 PM, Ted Creedon <tcree...@easystreet.net>wrote: > >> do I need a pointer to the sources for >> >> libgobject-2_0-0 - General-Purpose Utility Library -- Object-Oriented >> Framework for C? >> >> >> >> >> On Mon, Mar 3, 2014 at 3:47 PM, John Ralls <jra...@ceridwen.us> wrote: >> >>> >>> On Mar 3, 2014, at 3:30 PM, Ted Creedon <tcree...@easystreet.net> wrote: >>> >>> > Program received signal SIGSEGV, Segmentation fault. >>> > 0x00007fffef356cac in g_type_check_instance_is_a () from >>> > /usr/lib64/libgobject-2.0.so.0 >>> > >>> > >>> > can't do a bt because the fault freezes the X Screen >>> > >>> > had to ssh in from another box & kill -TERM gdb >>> > >>> > Should I do a debug build? >>> >>> Yes, of course. You'll also want the symbols and sources at least for >>> glib. >>> >>> Regards, >>> John Ralls >>> >>> >> > _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel