#112 Segmentation Fault on Paper Mode

Hello,

I used to use galculator and I get a segmentationFault following those steps :
1 - Open Galculator
2 - Pass to PaperMode
3 - On the keybord, press Control + P (Ctrl + P)

Galculator -v :
Compiled against GTK version 2.24.21
Linked against GTK version 2.24.23
Double-precision floating point numbers

Valgrind :
$> valgrind galculator
==16468== Memcheck, a memory error detector
==16468== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al.
==16468== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info
==16468== Command: galculator
==16468==
==16468== Invalid read of size 8
==16468== at 0x41587D: ??? (in /usr/bin/galculator)
==16468== by 0x416715: set_all_buttons_font (in /usr/bin/galculator)
==16468== by 0x4137F5: on_prefs_custom_button_font_toggled (in /usr/bin/galculator)
==16468== by 0x5983317: g_closure_invoke (in /usr/lib64/libgobject-2.0.so.0.3800.2)
==16468== by 0x5994CAC: ??? (in /usr/lib64/libgobject-2.0.so.0.3800.2)
==16468== by 0x599C9B8: g_signal_emit_valist (in /usr/lib64/libgobject-2.0.so.0.3800.2)
==16468== by 0x599CC71: g_signal_emit (in /usr/lib64/libgobject-2.0.so.0.3800.2)
==16468== by 0x4171C1: ui_pref_dialog_create (in /usr/bin/galculator)
==16468== by 0x5983317: g_closure_invoke (in /usr/lib64/libgobject-2.0.so.0.3800.2)
==16468== by 0x5994CAC: ??? (in /usr/lib64/libgobject-2.0.so.0.3800.2)
==16468== by 0x599C9B8: g_signal_emit_valist (in /usr/lib64/libgobject-2.0.so.0.3800.2)
==16468== by 0x599CC71: g_signal_emit (in /usr/lib64/libgobject-2.0.so.0.3800.2)
==16468== Address 0x0 is not stack'd, malloc'd or (recently) free'd
==16468==
==16468==
==16468== Process terminating with default action of signal 11 (SIGSEGV)
==16468== Access not within mapped region at address 0x0
==16468== at 0x41587D: ??? (in /usr/bin/galculator)
==16468== by 0x416715: set_all_buttons_font (in /usr/bin/galculator)
==16468== by 0x4137F5: on_prefs_custom_button_font_toggled (in /usr/bin/galculator)
==16468== by 0x5983317: g_closure_invoke (in /usr/lib64/libgobject-2.0.so.0.3800.2)
==16468== by 0x5994CAC: ??? (in /usr/lib64/libgobject-2.0.so.0.3800.2)
==16468== by 0x599C9B8: g_signal_emit_valist (in /usr/lib64/libgobject-2.0.so.0.3800.2)
==16468== by 0x599CC71: g_signal_emit (in /usr/lib64/libgobject-2.0.so.0.3800.2)
==16468== by 0x4171C1: ui_pref_dialog_create (in /usr/bin/galculator)
==16468== by 0x5983317: g_closure_invoke (in /usr/lib64/libgobject-2.0.so.0.3800.2)
==16468== by 0x5994CAC: ??? (in /usr/lib64/libgobject-2.0.so.0.3800.2)
==16468== by 0x599C9B8: g_signal_emit_valist (in /usr/lib64/libgobject-2.0.so.0.3800.2)
==16468== by 0x599CC71: g_signal_emit (in /usr/lib64/libgobject-2.0.so.0.3800.2)
==16468== If you believe this happened as a result of a stack
==16468== overflow in your program's main thread (unlikely but
==16468== possible), you can try to increase the size of the
==16468== main thread stack using the --main-stacksize= flag.
==16468== The main thread stack size used in this run was 8388608.
==16468==
==16468== HEAP SUMMARY:
==16468== in use at exit: 3,905,955 bytes in 63,240 blocks
==16468== total heap usage: 230,111 allocs, 166,871 frees, 29,495,147 bytes allocated
==16468==
==16468== LEAK SUMMARY:
==16468== definitely lost: 11,353 bytes in 57 blocks
==16468== indirectly lost: 53,809 bytes in 2,238 blocks
==16468== possibly lost: 89,408 bytes in 1,295 blocks
==16468== still reachable: 3,474,017 bytes in 58,260 blocks
==16468== suppressed: 0 bytes in 0 blocks
==16468== Rerun with --leak-check=full to see details of leaked memory
==16468==
==16468== For counts of detected and suppressed errors, rerun with: -v
==16468== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 2 from 2)
Processus arrêté

Thanks very much,

[Simon]

Hi, this bug has been fixed in SVN
thanks for your report