segmentation fault: additional info

[Derek Atkins]

Interesting.. It's actually dying in guile.  Weird..

And yes, the log replay issue should be filed separately.

-derek

Mark Johnson <mrj001 at shaw.ca> writes:

> My fault, I forgot to mention the version of gnucash.  It is 1.8.10.
> My version of guile is 1.6.4.  I believe that I installed slib version 2d6. 
> However, I failed to make a package for it or even to write the version in my
> notes.  I do have version 2d6 and 3a1 downloaded.  I am running Slackware version
> 10.0, patched with security patches.  The linux kernel version is 2.6.9.
>
> Here is the output from gdb when I run the report:
> Program received signal SIGSEGV, Segmentation fault.
> 0x4006d779 in scm_cons () from /usr/lib/libguile.so.12
>
> The output from "backtrace":
> #0  0x4006d779 in scm_cons () from /usr/lib/libguile.so.12
> #1  0x40045bfd in scm_deval () from /usr/lib/libguile.so.12
> #2  0x4004560a in scm_deval () from /usr/lib/libguile.so.12
> #3  0x4004610a in scm_deval () from /usr/lib/libguile.so.12
> #4  0x4004461e in scm_deval () from /usr/lib/libguile.so.12
> #5  0x40046295 in scm_deval () from /usr/lib/libguile.so.12
> #6  0x40046295 in scm_deval () from /usr/lib/libguile.so.12
> #7  0x40046295 in scm_deval () from /usr/lib/libguile.so.12
> #8  0x400457e9 in scm_deval () from /usr/lib/libguile.so.12
> #9  0x400441e2 in scm_deval_args () from /usr/lib/libguile.so.12
> #10 0x40045ce6 in scm_deval () from /usr/lib/libguile.so.12
> #11 0x4004571d in scm_deval () from /usr/lib/libguile.so.12
>
> [big snip of many lines like the above]
>
> #7667 0x400457e9 in scm_deval () from /usr/lib/libguile.so.12
> #7668 0x400457e9 in scm_deval () from /usr/lib/libguile.so.12
> #7669 0x400457e9 in scm_deval () from /usr/lib/libguile.so.12
> #7670 0x400457e9 in scm_deval () from /usr/lib/libguile.so.12
> #7671 0x400447e4 in scm_deval () from /usr/lib/libguile.so.12
> #7672 0x400457e9 in scm_deval () from /usr/lib/libguile.so.12
> #7673 0x400480ea in scm_dapply () from /usr/lib/libguile.so.12
> #7674 0x40043133 in scm_apply () from /usr/lib/libguile.so.12
> #7675 0x4005072f in gh_call0 () from /usr/lib/libguile.so.12
> #7676 0x4088781f in gnc_extension_run_script ()
>    from /usr/local/lib/gnucash/libgncmod-gnome-utils.so.0
> #7677 0x4061a877 in gtk_marshal_NONE__NONE () from /usr/lib/libgtk-1.2.so.0
> #7678 0x40649e5a in gtk_signal_remove_emission_hook ()
>    from /usr/lib/libgtk-1.2.so.0
> #7679 0x4064916a in gtk_signal_set_funcs () from /usr/lib/libgtk-1.2.so.0
> #7680 0x40647234 in gtk_signal_emit () from /usr/lib/libgtk-1.2.so.0
> #7681 0x4067d2ae in gtk_widget_activate () from /usr/lib/libgtk-1.2.so.0
> #7682 0x40622d9c in gtk_menu_shell_activate_item ()
>    from /usr/lib/libgtk-1.2.so.0
> #7683 0x4062204c in gtk_menu_shell_deactivate () from /usr/lib/libgtk-1.2.so.0
> #7684 0x4061a64d in gtk_marshal_BOOL__POINTER () from /usr/lib/libgtk-1.2.so.0
> #7685 0x4064919f in gtk_signal_set_funcs () from /usr/lib/libgtk-1.2.so.0
> #7686 0x40647234 in gtk_signal_emit () from /usr/lib/libgtk-1.2.so.0
> #7687 0x4067cfd9 in gtk_widget_event () from /usr/lib/libgtk-1.2.so.0
> #7688 0x4061a4d0 in gtk_propagate_event () from /usr/lib/libgtk-1.2.so.0
> #7689 0x406195c1 in gtk_main_do_event () from /usr/lib/libgtk-1.2.so.0
> #7690 0x406c1b44 in gdk_wm_protocols_filter () from /usr/lib/libgdk-1.2.so.0
> #7691 0x40319e75 in g_get_current_time () from /usr/lib/libglib-1.2.so.0
> #7692 0x4031a32c in g_get_current_time () from /usr/lib/libglib-1.2.so.0
> #7693 0x4031a55c in g_main_run () from /usr/lib/libglib-1.2.so.0
> #7694 0x40619083 in gtk_main () from /usr/lib/libgtk-1.2.so.0
> #7695 0x4036afd2 in gnc_ui_start_event_loop ()
>    from /usr/local/lib/libgncgnome.so.0
> #7696 0x00002710 in ?? ()
> #7697 0x4036ae60 in gnc_gui_destroy () from /usr/local/lib/libgncgnome.so.0
> Previous frame inner to this frame (corrupt stack?)
>
> I'm not sure whether that last line is more significant than the extreme
> recursion.  I suspect this is all a clue.
>
> I filed Bug #165571 to request additional information in the warnings.  I wonder: 
> should I file one against the log replay since it seems to be responsible for
> losing the currency of the transaction?  Or is this known?
>
> Mark

-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord at MIT.EDU                        PGP key available