After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 372711 - [WIN XP] msvcrt.dll crash while trying to reference cells between files
[WIN XP] msvcrt.dll crash while trying to reference cells between files
Status: RESOLVED DUPLICATE of bug 367870
Product: Gnumeric
Classification: Applications
Component: General
1.7.x
Other All
: Normal critical
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2006-11-08 22:28 UTC by A
Modified: 2006-11-09 01:30 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
a picture of things crashing (73.97 KB, image/gif)
2006-11-08 22:29 UTC, A 		Details
the file that was sent to microsoft in the error report - is this a useful thing to include here? (25.70 KB, text/plain)
2006-11-08 22:32 UTC, A 		Details
this is the drwatson output (29.57 KB, text/plain)
2006-11-09 01:30 UTC, A 		Details

Description A 2006-11-08 22:28:34 UTC 
Steps to reproduce:
1. create 2 gnumeric files, i'll call them File1 and File2
2. in File2 cell A1 try to type a reference to a cell in File1
3. File2 dies a gruesome death

the crash happens when you type the "]" character, it doesn't seem to mind what is between "[" and "]" but it doesn't crash if there is nothing between the square brackets


Stack trace:
tell me how to get a stack trace in windows and I will gladly provide it

Other information:
see attached
Comment 1 A 2006-11-08 22:29:49 UTC 
Created attachment 76238 [details]
a picture of things crashing
Comment 2 A 2006-11-08 22:32:06 UTC 
Created attachment 76239 [details]
the file that was sent to microsoft in the error report - is this a useful thing to include here?

this is on gnumeric V 1.7.1 thanks !
Comment 3 Morten Welinder 2006-11-08 23:09:23 UTC 
In this particular example, the file is not useful.  It tells us, basically,
when versions of things are in use.

You might be able to make a cross-workbook link using cut-and-paste.
Comment 4 sum1 2006-11-08 23:31:25 UTC 
(In reply to comment #0)
> Steps to reproduce:
> 1. create 2 gnumeric files, i'll call them File1 and File2
> 2. in File2 cell A1 try to type a reference to a cell in File1
> 3. File2 dies a gruesome death

With 1.7.1 on Windows, I get a crash if I just type "=[f]" in a cell.

> 
> Stack trace:
> tell me how to get a stack trace in windows and I will gladly provide it

You can get a stack trace with Dr. Watson:
- Start > Run
- Type "drwtsn32" and press enter
- Double-click on the relevant Gnumeric entry in the "Application Errors" section
- Scroll to the "*----> Stack Back Trace <----*" section and copy the stack frames (for this crash, you'll see MSVCRT!strcmp at the top)


In case it's needed, here's a non-debug backtrace from gdb:

Program received signal SIGSEGV, Segmentation fault.
0x77c47742 in strcmp () from C:\WINDOWS\system32\msvcrt.dll
(gdb) bt

+ Trace 84569

  • #0 strcmp
    from C:\WINDOWS\system32\msvcrt.dll
  • #1 libspreadsheet-1-7-1!gnm_app_clipboard_area_get
    from c:\Gnumeric\bin\libspreadsheet-1-7-1.dll
  • #2 libspreadsheet-1-7-1!gnm_app_workbook_get_by_name
    from c:\Gnumeric\bin\libspreadsheet-1-7-1.dll
  • #3 parse_error_free
    from c:\Gnumeric\bin\libspreadsheet-1-7-1.dll
  • #4 rangeref_parse
    from c:\Gnumeric\bin\libspreadsheet-1-7-1.dll
  • #5 libspreadsheet-1-7-1!gnm_expr_expr_find_range
    from c:\Gnumeric\bin\libspreadsheet-1-7-1.dll
  • #6 libspreadsheet-1-7-1!gnm_expr_entry_can_rangesel
    from c:\Gnumeric\bin\libspreadsheet-1-7-1.dll
  • #7 libspreadsheet-1-7-1!gnm_expr_entry_can_rangesel
    from c:\Gnumeric\bin\libspreadsheet-1-7-1.dll
  • #8 libgobject-2!g_closure_invoke
    from c:\Gnumeric\bin\libgobject-2.0-0.dll
  • #9 libgobject-2!g_signal_has_handler_pending
    from c:\Gnumeric\bin\libgobject-2.0-0.dll
  • #10 libgobject-2!g_signal_emit_valist
    from c:\Gnumeric\bin\libgobject-2.0-0.dll
  • #11 libgobject-2!g_signal_emit_by_name
    from c:\Gnumeric\bin\libgobject-2.0-0.dll
  • #12 libgtk-win32-2!gtk_entry_set_visibility
    from c:\Gnumeric\bin\libgtk-win32-2.0-0.dll
  • #13 libgobject-2!g_closure_invoke
    from c:\Gnumeric\bin\libgobject-2.0-0.dll
  • #14 libgobject-2!g_signal_has_handler_pending
    from c:\Gnumeric\bin\libgobject-2.0-0.dll
  • #15 libgobject-2!g_signal_emit_valist
    from c:\Gnumeric\bin\libgobject-2.0-0.dll
  • #16 libgobject-2!g_signal_emit_by_name
    from c:\Gnumeric\bin\libgobject-2.0-0.dll
  • #17 libgtk-win32-2!gtk_entry_get_type
    from c:\Gnumeric\bin\libgtk-win32-2.0-0.dll
  • #18 libspreadsheet-1-7-1!gnm_simple_canvas_grab
    from c:\Gnumeric\bin\libspreadsheet-1-7-1.dll
  • #19 libgobject-2!g_closure_invoke
    from c:\Gnumeric\bin\libgobject-2.0-0.dll
  • #20 libgobject-2!g_signal_has_handler_pending
    from c:\Gnumeric\bin\libgobject-2.0-0.dll
  • #21 libgobject-2!g_signal_emit_valist
    from c:\Gnumeric\bin\libgobject-2.0-0.dll
  • #22 libgobject-2!g_signal_emit_by_name
    from c:\Gnumeric\bin\libgobject-2.0-0.dll
  • #23 libgobject-2!g_closure_invoke
    from c:\Gnumeric\bin\libgobject-2.0-0.dll
  • #24 libgobject-2!g_signal_has_handler_pending
    from c:\Gnumeric\bin\libgobject-2.0-0.dll
  • #25 libgobject-2!g_signal_emit_valist
    from c:\Gnumeric\bin\libgobject-2.0-0.dll
  • #26 libgobject-2!g_signal_emit_by_name
    from c:\Gnumeric\bin\libgobject-2.0-0.dll
  • #27 libgtk-win32-2!gtk_im_context_simple_new
    from c:\Gnumeric\bin\libgtk-win32-2.0-0.dll
  • #28 libspreadsheet-1-7-1!gnm_canvas_get_type
    from c:\Gnumeric\bin\libspreadsheet-1-7-1.dll
  • #29 libgtk-win32-2!gtk_marshal_VOID__UINT_STRING
    from c:\Gnumeric\bin\libgtk-win32-2.0-0.dll
  • #30 libgobject-2!g_closure_invoke
    from c:\Gnumeric\bin\libgobject-2.0-0.dll
  • #31 libgobject-2!g_signal_has_handler_pending
    from c:\Gnumeric\bin\libgobject-2.0-0.dll
  • #32 libgobject-2!g_signal_emit_valist
    from c:\Gnumeric\bin\libgobject-2.0-0.dll
  • #33 libgobject-2!g_signal_emit
    from c:\Gnumeric\bin\libgobject-2.0-0.dll
  • #34 libgtk-win32-2!gtk_widget_activate
    from c:\Gnumeric\bin\libgtk-win32-2.0-0.dll
  • #35 libgtk-win32-2!gtk_window_propagate_key_event
    from c:\Gnumeric\bin\libgtk-win32-2.0-0.dll
  • #36 libgtk-win32-2!gtk_window_activate_key
    from c:\Gnumeric\bin\libgtk-win32-2.0-0.dll
  • #37 libgtk-win32-2!gtk_marshal_VOID__UINT_STRING
    from c:\Gnumeric\bin\libgtk-win32-2.0-0.dll
  • #38 libgobject-2!g_closure_invoke
    from c:\Gnumeric\bin\libgobject-2.0-0.dll
  • #39 libgobject-2!g_signal_has_handler_pending
    from c:\Gnumeric\bin\libgobject-2.0-0.dll
  • #40 libgobject-2!g_signal_emit_valist
    from c:\Gnumeric\bin\libgobject-2.0-0.dll
  • #41 libgobject-2!g_signal_emit
    from c:\Gnumeric\bin\libgobject-2.0-0.dll
  • #42 libgtk-win32-2!gtk_widget_activate
    from c:\Gnumeric\bin\libgtk-win32-2.0-0.dll
  • #43 libgtk-win32-2!gtk_propagate_event
    from c:\Gnumeric\bin\libgtk-win32-2.0-0.dll
  • #44 libgtk-win32-2!gtk_main_do_event
    from c:\Gnumeric\bin\libgtk-win32-2.0-0.dll
  • #45 libgdk-win32-2!gdk_event_get_graphics_expose
    from c:\Gnumeric\bin\libgdk-win32-2.0-0.dll
  • #46 libglib-2!g_source_remove_poll
    from c:\Gnumeric\bin\libglib-2.0-0.dll
  • #47 libglib-2!g_main_context_acquire
    from c:\Gnumeric\bin\libglib-2.0-0.dll
  • #48 libglib-2!g_main_loop_run
    from c:\Gnumeric\bin\libglib-2.0-0.dll
  • #49 libgtk-win32-2!gtk_main
    from c:\Gnumeric\bin\libgtk-win32-2.0-0.dll 






Comment 5


A





          2006-11-09 00:31:05 UTC
        



cut and paste only pastes the contents of the cell, not a reference, so unfortuinately that isn't a workaround. :|

the "Application Errors" section in Dr watson remains empty during this crash. do I need to initiate it or something?






Comment 6


sum1





          2006-11-09 00:53:47 UTC
        



(In reply to comment #5)
> the "Application Errors" section in Dr watson remains empty during this crash.
> do I need to initiate it or something?
> 

On my system, it shows up after I hit "Don't Send." If you're sending the report to Microsoft, it might not show up afterward (I never do, so I'm not sure). In case it helps, I have the "Number of Instructions" and "Number of Errors To Save" each set to 25, and "Dump All Thread Contexts," "Append to Existing Log File," and "Create Crash Dump File" checked.






Comment 7


Morten Welinder





          2006-11-09 01:21:49 UTC
        



I would risk a bet that this is the same crash as over in bug 367870.


*** This bug has been marked as a duplicate of 367870 ***






Comment 8


A





          2006-11-09 01:30:28 UTC
        



Created attachment 76247 [details]
this is the drwatson output

i got it by following the "crash dump" path