Bug 528653 – gcalctool crashed with SIGSEGV in strncpy()

Bug 528653 - gcalctool crashed with SIGSEGV in strncpy()


Summary:	gcalctool crashed with SIGSEGV in strncpy()

Status:	RESOLVED DUPLICATE of bug 527545

Product:	gnome-calculator
Classification:	Core
Component:	general
Version:	5.22.x
Hardware:	Other All

Importance:	Normal critical
Target Milestone:	---
Assigned To:	gcalctool maintainers
QA Contact:	gcalctool maintainers

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:
	Show dependency tree

Reported:	2008-04-17 20:57 UTC by Greg Grossmeier
Modified:	2008-04-19 03:11 UTC (History)
CC List:	3 users (show)

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Greg Grossmeier 2008-04-17 20:57:53 UTC

Steps to reproduce:
Originally opened on Launchpad: https://launchpad.net/bugs/218772
-----
1. Scientific mode, flick "Fun" button
2. Edit functions, add value to the 0 function
3. Click OK
4. gcalctool crashes, producing a .crash file (see Launchpad for more diagnosis).



Stack trace:

+ Trace 195500

#0 strncpy
from /lib/libc.so.6
#1 ??
#2 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#3 ??
from /usr/lib/libgobject-2.0.so.0
#4 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#5 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#6 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#7 ??
from /usr/lib/libgobject-2.0.so.0
#8 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#9 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#10 ??
from /usr/lib/libgtk-x11-2.0.so.0
#11 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#12 ??
from /usr/lib/libgobject-2.0.so.0
#13 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#15 ??
from /usr/lib/libgtk-x11-2.0.so.0
#16 ??
from /usr/lib/libgtk-x11-2.0.so.0
#17 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#18 ??
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#21 ??
from /usr/lib/libgtk-x11-2.0.so.0
#22 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#23 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#24 ??
from /usr/lib/libgdk-x11-2.0.so.0
#25 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#26 ??
from /usr/lib/libglib-2.0.so.0
#27 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#28 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#29 ??
#30 __libc_start_main
from /lib/libc.so.6
#31 ??
#32 ??
#33 ??


Other information:
$apt-cache policy gcalctool
gcalctool:
  Installed: 5.22.1-0ubuntu1
  Candidate: 5.22.1-0ubuntu1

Comment 1 Greg Grossmeier 2008-04-17 21:00:29 UTC

I was able to confirm this crash as well.

Comment 2 Pedro Villavicencio 2008-04-18 00:10:09 UTC

Better stacktrace:

+ Trace 195506

Thread 1 (Thread 0xb71e5940 (LWP 7985))

#0 strncpy
from /lib/tls/i686/cmov/libc.so.6
#1 edit_functions_response_cb
at gtk.c line 1570
#2 IA__g_cclosure_marshal_VOID__INT
at /build/buildd/glib2.0-2.16.3/gobject/gmarshal.c line 216
#3 IA__g_closure_invoke
at /build/buildd/glib2.0-2.16.3/gobject/gclosure.c line 490
#4 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.16.3/gobject/gsignal.c line 2440
#5 IA__g_signal_emit_valist
at /build/buildd/glib2.0-2.16.3/gobject/gsignal.c line 2199
#6 IA__g_signal_emit
at /build/buildd/glib2.0-2.16.3/gobject/gsignal.c line 2243
#7 IA__gtk_dialog_response
at /build/buildd/gtk+2.0-2.12.9/gtk/gtkdialog.c line 879
#8 IA__g_cclosure_marshal_VOID__VOID
at /build/buildd/glib2.0-2.16.3/gobject/gmarshal.c line 77
#9 IA__g_closure_invoke
at /build/buildd/glib2.0-2.16.3/gobject/gclosure.c line 490
#10 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.16.3/gobject/gsignal.c line 2440
#11 IA__g_signal_emit_valist
at /build/buildd/glib2.0-2.16.3/gobject/gsignal.c line 2199
#12 IA__g_signal_emit
at /build/buildd/glib2.0-2.16.3/gobject/gsignal.c line 2243
#13 IA__gtk_button_clicked
at /build/buildd/gtk+2.0-2.12.9/gtk/gtkbutton.c line 889
#14 gtk_real_button_released
at /build/buildd/gtk+2.0-2.12.9/gtk/gtkbutton.c line 1484
#15 IA__g_cclosure_marshal_VOID__VOID
at /build/buildd/glib2.0-2.16.3/gobject/gmarshal.c line 77
#16 g_type_class_meta_marshal
at /build/buildd/glib2.0-2.16.3/gobject/gclosure.c line 567
#17 IA__g_closure_invoke
at /build/buildd/glib2.0-2.16.3/gobject/gclosure.c line 490
#18 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.16.3/gobject/gsignal.c line 2370
#19 IA__g_signal_emit_valist
at /build/buildd/glib2.0-2.16.3/gobject/gsignal.c line 2199
#20 IA__g_signal_emit
at /build/buildd/glib2.0-2.16.3/gobject/gsignal.c line 2243
#21 IA__gtk_button_released
at /build/buildd/gtk+2.0-2.12.9/gtk/gtkbutton.c line 881
#22 gtk_button_button_release
at /build/buildd/gtk+2.0-2.12.9/gtk/gtkbutton.c line 1377
#23 _gtk_marshal_BOOLEAN__BOXED
at /build/buildd/gtk+2.0-2.12.9/gtk/gtkmarshalers.c line 84
#24 g_type_class_meta_marshal
at /build/buildd/glib2.0-2.16.3/gobject/gclosure.c line 567
#25 IA__g_closure_invoke
at /build/buildd/glib2.0-2.16.3/gobject/gclosure.c line 490
#26 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.16.3/gobject/gsignal.c line 2478
#27 IA__g_signal_emit_valist
at /build/buildd/glib2.0-2.16.3/gobject/gsignal.c line 2209
#28 IA__g_signal_emit
at /build/buildd/glib2.0-2.16.3/gobject/gsignal.c line 2243
#29 gtk_widget_event_internal
at /build/buildd/gtk+2.0-2.12.9/gtk/gtkwidget.c line 4678
#30 IA__gtk_propagate_event
at /build/buildd/gtk+2.0-2.12.9/gtk/gtkmain.c line 2336
#31 IA__gtk_main_do_event
at /build/buildd/gtk+2.0-2.12.9/gtk/gtkmain.c line 1556
#32 gdk_event_dispatch
at /build/buildd/gtk+2.0-2.12.9/gdk/x11/gdkevents-x11.c line 2351
#33 IA__g_main_context_dispatch
at /build/buildd/glib2.0-2.16.3/glib/gmain.c line 2009
#34 g_main_context_iterate
at /build/buildd/glib2.0-2.16.3/glib/gmain.c line 2642
#35 IA__g_main_loop_run
at /build/buildd/glib2.0-2.16.3/glib/gmain.c line 2850
#36 IA__gtk_main
at /build/buildd/gtk+2.0-2.12.9/gtk/gtkmain.c line 1163
#37 main
at calctool.c line 769

Comment 3 Robert Ancell 2008-04-19 03:11:09 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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

Note You need to log in before you can comment on or make changes to this bug.