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 628259 - Crash on opening file with charts
Crash on opening file with charts
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: Charting
1.10.x
Other All
: High blocker
: ---
Assigned To: Jean Bréfort
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2010-08-29 17:56 UTC by Paul Nielsen
Modified: 2010-08-30 12:55 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
File with multiple sheets and plots which can't be opened with 1.10.8 and 1.10.9, and windows error report (94.34 KB, application/octet-stream)
2010-08-29 17:56 UTC, Paul Nielsen 		Details
dr watson crash log (265.15 KB, application/x-zip-compressed)
2010-08-29 18:37 UTC, Paul Nielsen 		Details

Description Paul Nielsen 2010-08-29 17:56:49 UTC 
Created attachment 169008 [details]
File with multiple sheets and plots which can't be opened with 1.10.8 and 1.10.9, and windows error report

When trying to open numerous files which were created in Gnumeric 1.10.6 and earlier there is an unspecified crash of Gnumeric 1.10.8 and 1.10.9.  1.10.9 runs in Win2k (unlike 1.10.8), but also crashes when opening the file.

Sample file attached together with Windows error report from WinXP (SP2).
Comment 1 Paul Nielsen 2010-08-29 18:37:34 UTC 
Created attachment 169009 [details]
dr watson crash log

These are the Dr Watson crash logs for the example file attached previously.  They report a divide by zero occurring with both Win2K and WinXP.  I noticed that the "321c_appcompat.txt" attached previously with the example file doesn't seem to have much useful information in it.
Comment 2 Andreas J. Guelzow 2010-08-29 19:55:45 UTC 
We are lucky. This is also crashing on Linux.
Comment 3 Andreas J. Guelzow 2010-08-29 19:59:11 UTC 



+
Trace
    223462






    

  • 
#0
map_week_calc_ticks

    
                at gog-axis.c
                  line
                  826

    

    • 

  • 
#1
map_date_calc_ticks

    
                at gog-axis.c
                  line
                  913

    

    • 

  • 
#2
gog_axis_calc_ticks

    
                at gog-axis.c
                  line
                  1771

    

    • 

  • 
#3
gog_axis_update

    
                at gog-axis.c
                  line
                  2192

    

    • 

  • 
#4
gog_axis_dim_changed

    
                at gog-axis.c
                  line
                  2643

    

    • 

  • 
#5
cb_dataset_dim_changed

    
                at gog-data-set.c
                  line
                  142

    

    • 

  • 
#6
g_cclosure_marshal_VOID__VOID

    
                from
                /usr/lib/libgobject-2.0.so.0

    

    • 

  • 
#7
g_closure_invoke

    
                from
                /usr/lib/libgobject-2.0.so.0

    

    • 

  • 
#8
??

    
                from
                /usr/lib/libgobject-2.0.so.0

    

    • 

  • 
#9
g_signal_emit_valist

    
                from
                /usr/lib/libgobject-2.0.so.0

    

    • 

  • 
#10
g_signal_emit

    
                from
                /usr/lib/libgobject-2.0.so.0

    

    • 

  • 
#11
go_data_emit_changed

    
                at go-data.c
                  line
                  228

    

    • 

  • 
#12
gnm_go_data_set_sheet

    
                at graph.c
                  line
                  268

    

    • 













Comment 4


Andreas J. Guelzow





          2010-08-29 20:02:18 UTC
        



(gdb) p maj_days
$1 = 0
(gdb) p min_days
$2 = 0
(gdb)






Comment 5


Morten Welinder





          2010-08-30 00:26:27 UTC
        



The problem was not in map_week_calc_ticks but in the fact that it got there.

This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.

Note: the fix is in goffice, not gnumeric.






Comment 6


Morten Welinder





          2010-08-30 12:55:41 UTC
        



If you need access to the data before the next release, you can edit
the xml by hand.  In this case, it isn't hard:

0. Make a backup
1. Rename PressureAltitudeTests-20100825.gnumeric to pat.gz
2. gzip -d pat.gz
3. Edit pat and change two occurrences of 0.04166... to 1
4. gzip pat
5. Rename back.