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 735555 - Segfault when trying to create statistic plot
Segfault when trying to create statistic plot
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: Charting
1.12.x
Other Linux
: Normal normal
: ---
Assigned To: Jean Bréfort
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2014-08-27 22:19 UTC by fxTW7H5rJ1gh
Modified: 2014-08-28 15:54 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
minimal test case (1.75 KB, application/octet-stream)
2014-08-27 22:19 UTC, fxTW7H5rJ1gh
Details
gdb bt full.log (4.59 KB, application/octet-stream)
2014-08-28 15:44 UTC, fxTW7H5rJ1gh
Details

Description fxTW7H5rJ1gh 2014-08-27 22:19:33 UTC
Created attachment 284642 [details]
minimal test case

1) Have the following fields:

B1: Any text
B2: Any number
A3: Any number

I attached a spreadsheet with a minimal example.

2) Select the 2x3 cells from A1 to B3.

3) Click the graph icon.

4) Select Statistics.

5) Gnumeric crashes.

For me it printed this to the terminal:
(gnumeric:12488): GLib-CRITICAL **: g_strtod: assertion 'nptr != NULL' failed

And dmesg shows me:
gnumeric[12488]: segfault at a0 ip 00007fb6f38b2eda sp 00007fff23ab93d0 error 4 in libgoffice-0.10.so.10.0.17[7fb6f383f000+19a000]

---
Gnumeric 1.12.17 on 64 bit Archlinux. Tested with libgoffice 0.10.17-1 as well as libgoffice built from git on 2014-08-18 or -19, both crashed. I am not sure if this is a gnumeric or libgoffice bug.
Comment 1 Andreas J. Guelzow 2014-08-28 02:24:14 UTC
I do not get a crash but the same critical:

Breakpoint 1, g_log (log_domain=log_domain@entry=0x7ffff669a5ae "GLib", 
    log_level=log_level@entry=G_LOG_LEVEL_CRITICAL, 
    format=format@entry=0x7ffff66a43aa "%s: assertion '%s' failed")
    at /build/buildd/glib2.0-2.38.1/./glib/gmessages.c:1021
1021	/build/buildd/glib2.0-2.38.1/./glib/gmessages.c: No such file or directory.
(gdb) bt
  • #0 g_log
    at /build/buildd/glib2.0-2.38.1/./glib/gmessages.c line 1021
  • #1 g_return_if_fail_warning
    at /build/buildd/glib2.0-2.38.1/./glib/gmessages.c line 1034
  • #2 g_strtod
    at /build/buildd/glib2.0-2.38.1/./glib/gstrfuncs.c line 634
  • #3 go_data_vector_str_get_value
    at data/go-data-simple.c line 684
  • #4 go_data_get_vector_value
    at data/go-data.c line 524
  • #5 map_discrete_calc_ticks
    at graph/gog-axis.c line 497
  • #6 gog_axis_calc_ticks
    at graph/gog-axis.c line 2111
  • #7 gog_axis_update
    at graph/gog-axis.c line 2676
  • #8 gog_object_update

Comment 2 Jean Bréfort 2014-08-28 07:03:09 UTC
The critical is not harmful by itself (g_strtod returns 0). It can easily be fixed but this does not explain the crash. A stack trace of the crash would be useful as I can't reproduce it either.
Comment 3 Andreas J. Guelzow 2014-08-28 07:33:53 UTC
Did you build Gnumeric with Critical turned into Assertions?
Comment 4 fxTW7H5rJ1gh 2014-08-28 09:27:15 UTC
I don't know.

https://www.archlinux.org/packages/extra/x86_64/gnumeric/ is the package I use. I reproduced the bug on a 32 bit Archlinux as well.

You can see the build options here: https://projects.archlinux.org/svntogit/packages.git/tree/trunk?h=packages/gnumeric in the PKGBUILD and the patch.
Comment 5 Morten Welinder 2014-08-28 12:15:29 UTC
That Gnumeric isn't built right.  This patch is wrong and can easily cause
weird crashes:

https://projects.archlinux.org/svntogit/packages.git/tree/trunk/revert-warnings.patch?h=packages/gnumeric
Comment 6 fxTW7H5rJ1gh 2014-08-28 15:44:21 UTC
With Jean's help I built both goffice and gnumeric from git using:
https://aur.archlinux.org/packages/gn/gnumeric-git/PKGBUILD
https://aur.archlinux.org/packages/go/goffice-git/PKGBUILD
with the addition of CPPFLAGS="-g" for autogen.sh

Then triggered the crash in gdb. See the attached file for the log.
Comment 7 fxTW7H5rJ1gh 2014-08-28 15:44:40 UTC
Created attachment 284718 [details]
gdb bt full.log
Comment 8 Jean Bréfort 2014-08-28 15:54:12 UTC
This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.