Bug 570505 – file-roller crashed with signal 5 in IA__g_malloc()

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 570505 - file-roller crashed with signal 5 in IA__g_malloc()


Summary:	file-roller crashed with signal 5 in IA__g_malloc()


Status:	RESOLVED FIXED

Product:	file-roller
Classification:	Applications
Component:	general
Version:	2.25.x
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	---
Assigned To:	Paolo Bacchilega
QA Contact:	file-roller-maint

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2009-02-04 15:51 UTC by Pedro Villavicencio
Modified:	2009-02-04 18:14 UTC

See Also:
GNOME target:	---
GNOME version:	2.25/2.26

Attachments
valgring log (303.75 KB, text/plain) 2009-02-04 15:52 UTC, Pedro Villavicencio	Details

Description Pedro Villavicencio 2009-02-04 15:51:35 UTC

steps to reproduce it:

1- open file roller and click on New
2- enter some text in the text field
3- select tar compressed with bzip2 from the archive type

stacktrace:

".

+ Trace 212222

Thread 1 (process 23788)

#0 IA__g_logv
at /build/buildd/glib2.0-2.19.6/glib/gmessages.c line 503
#1 IA__g_log
at /build/buildd/glib2.0-2.19.6/glib/gmessages.c line 517
#2 IA__g_malloc
at /build/buildd/glib2.0-2.19.6/glib/gmem.c line 135
#3 IA__g_strndup
at /build/buildd/glib2.0-2.19.6/glib/gstrfuncs.c line 155
#4 archive_type_combo_box_changed_cb
at dlg-new.c line 157
#5 IA__g_cclosure_marshal_VOID__VOID
at /build/buildd/glib2.0-2.19.6/gobject/gmarshal.c line 77
#6 IA__g_closure_invoke
at /build/buildd/glib2.0-2.19.6/gobject/gclosure.c line 767
#7 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.19.6/gobject/gsignal.c line 3244
#8 IA__g_signal_emit_valist
at /build/buildd/glib2.0-2.19.6/gobject/gsignal.c line 2977
#9 IA__g_signal_emit
at /build/buildd/glib2.0-2.19.6/gobject/gsignal.c line 3034
#10 ??
from /usr/lib/libgtk-x11-2.0.so.0
#11 gtk_combo_box_set_active_iter
from /usr/lib/libgtk-x11-2.0.so.0
#12 ??
from /usr/lib/libgtk-x11-2.0.so.0
#13 IA__g_cclosure_marshal_VOID__VOID
at /build/buildd/glib2.0-2.19.6/gobject/gmarshal.c line 77
#14 IA__g_closure_invoke
at /build/buildd/glib2.0-2.19.6/gobject/gclosure.c line 767
#15 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.19.6/gobject/gsignal.c line 3244
#16 IA__g_signal_emit_valist
at /build/buildd/glib2.0-2.19.6/gobject/gsignal.c line 2977
#17 IA__g_signal_emit
at /build/buildd/glib2.0-2.19.6/gobject/gsignal.c line 3034
#18 gtk_widget_activate
from /usr/lib/libgtk-x11-2.0.so.0
#19 gtk_menu_shell_activate_item
from /usr/lib/libgtk-x11-2.0.so.0
#20 ??
from /usr/lib/libgtk-x11-2.0.so.0
#21 ??
from /usr/lib/libgtk-x11-2.0.so.0
#22 ??
from /usr/lib/libgtk-x11-2.0.so.0
#23 g_type_class_meta_marshal
at /build/buildd/glib2.0-2.19.6/gobject/gclosure.c line 878
#24 IA__g_closure_invoke
at /build/buildd/glib2.0-2.19.6/gobject/gclosure.c line 767
#25 signal_emit_unlocked_R
at /build/buildd/glib2.0-2.19.6/gobject/gsignal.c line 3282
#26 IA__g_signal_emit_valist
at /build/buildd/glib2.0-2.19.6/gobject/gsignal.c line 2987
#27 IA__g_signal_emit
at /build/buildd/glib2.0-2.19.6/gobject/gsignal.c line 3034
#28 ??
from /usr/lib/libgtk-x11-2.0.so.0
#29 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#30 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#31 ??
from /usr/lib/libgdk-x11-2.0.so.0
#32 IA__g_main_context_dispatch
at /build/buildd/glib2.0-2.19.6/glib/gmain.c line 1814
#33 g_main_context_iterate
at /build/buildd/glib2.0-2.19.6/glib/gmain.c line 2448
#34 IA__g_main_loop_run
at /build/buildd/glib2.0-2.19.6/glib/gmain.c line 2656
#35 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#36 main
at main.c line 309

Comment 1 Pedro Villavicencio 2009-02-04 15:52:17 UTC

Created attachment 127929 [details]
valgring log

Comment 2 Paolo Bacchilega 2009-02-04 18:14:40 UTC

This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.