GNOME Bugzilla – Bug 382640
[win 32] crash on msvcrt.dll while altering chart axis title
Last modified: 2007-01-08 01:41:46 UTC
Steps to reproduce: create an XYplot properties > Y-axis > add > label > data > text type in: Bending Stress [psi] the crash happens while typing the closing square bracket Stack trace: Microsoft has it: http://msdn.microsoft.com/isv/resources/wer/ I tried to cut/paste it out of the error report, but the text was un-selectable :( here is information from the report: AppName: gnumeric.exe AppVer: 0.0.0.0 ModName: msvcrt.dll ModVer: 7.0.2600.2180 Offset: 00037742 Other information:
Thanks for this report. I can't reproduce this bug on linux. Does the crash happen every time ? If it's not possible to copy the error report, could you attach a screenshot of the report dialog ?
Created attachment 77809 [details] picture of error
it does happen every time
This bug might be a duplicate of Bug 367870 and Bug 372711. *----> Stack Back Trace <----* MSVCRT!strcmp+0x12 libspreadsheet-1-7-1!gnm_app_workbook_get_by_name+0x132 libspreadsheet-1-7-1!parse_error_free+0x189 libspreadsheet-1-7-1!rangeref_parse+0x3b libspreadsheet-1-7-1!gnm_expr_expr_find_range+0x14c libspreadsheet-1-7-1!gnm_expr_entry_can_rangesel+0x93 libspreadsheet-1-7-1!gnm_expr_entry_can_rangesel+0x2f9 libgobject-2.0-0!g_closure_invoke+0xf6 libgobject-2.0-0!g_signal_has_handler_pending+0xec4 libgobject-2.0-0!g_signal_emit_valist+0x78a libgobject-2.0-0!g_signal_emit_by_name+0x8f libgtk-win32-2.0-0!gtk_entry_set_visibility+0x1e21 libgobject-2.0-0!g_closure_invoke+0xf6 libgobject-2.0-0!g_signal_has_handler_pending+0xaf8 libgobject-2.0-0!g_signal_emit_valist+0x78a libgobject-2.0-0!g_signal_emit_by_name+0x8f libgtk-win32-2.0-0!gtk_entry_get_type+0x1439 libgtk-win32-2.0-0!gtk_entry_set_visibility+0x2df5 libgobject-2.0-0!g_closure_invoke+0xf6 libgobject-2.0-0!g_signal_has_handler_pending+0xec4 libgobject-2.0-0!g_signal_emit_valist+0x78a libgobject-2.0-0!g_signal_emit_by_name+0x8f libgobject-2.0-0!g_closure_invoke+0xf6 libgobject-2.0-0!g_signal_has_handler_pending+0xec4 libgobject-2.0-0!g_signal_emit_valist+0x78a libgobject-2.0-0!g_signal_emit_by_name+0x8f libgtk-win32-2.0-0!gtk_im_context_simple_new+0x8aa libgtk-win32-2.0-0!gtk_entry_set_visibility+0x386c libgtk-win32-2.0-0!gtk_marshal_VOID__UINT_STRING+0x111 libgobject-2.0-0!g_closure_invoke+0xf6 libgobject-2.0-0!g_signal_has_handler_pending+0xaf8 libgobject-2.0-0!g_signal_emit_valist+0x4f7 libgobject-2.0-0!g_signal_emit+0x1a libgtk-win32-2.0-0!gtk_widget_activate+0x1d7 libgtk-win32-2.0-0!gtk_window_propagate_key_event+0x103 libgtk-win32-2.0-0!gtk_window_activate_key+0x3bb libgtk-win32-2.0-0!gtk_marshal_VOID__UINT_STRING+0x111 libgobject-2.0-0!g_closure_invoke+0xf6 libgobject-2.0-0!g_signal_has_handler_pending+0xaf8 libgobject-2.0-0!g_signal_emit_valist+0x4f7 libgobject-2.0-0!g_signal_emit+0x1a libgtk-win32-2.0-0!gtk_widget_activate+0x1d7 libgtk-win32-2.0-0!gtk_propagate_event+0x1a3 libgtk-win32-2.0-0!gtk_main_do_event+0x239 libgdk-win32-2.0-0!gdk_event_get_graphics_expose+0x498d libglib-2.0-0!g_source_remove_poll+0x2b6 libglib-2.0-0!g_main_context_acquire+0x55f libglib-2.0-0!g_main_loop_run+0x159 libgtk-win32-2.0-0!gtk_main+0xa8 gnumeric+0x2794 gnumeric+0x1236 gnumeric+0x1288 kernel32!RegisterWaitForInputIdle+0x49
I can't seem to reproduce this bug anymore (with 1.7.6 on Windows XP).
The stack trace looks very much like a dupe of bug 367870. *** This bug has been marked as a duplicate of 367870 ***