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 336854 - crash on twice unpacking to the same location
crash on twice unpacking to the same location
Status: RESOLVED FIXED
Product: file-roller
Classification: Applications
Component: general
2.14.x
Other All
: Normal critical
: ---
Assigned To: Paolo Bacchilega
file-roller-maint
Depends on:
Blocks:
 
 
Reported: 2006-04-01 16:48 UTC by Marinus Schraal
Modified: 2006-04-04 11:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description Marinus Schraal 2006-04-01 16:48:50 UTC 
Steps to reproduce:
1. unpack an archive to a chosen location
2. hit the unpack button again and unpack to the same location


Stack trace:
Backtrace was generated from '/usr/bin/file-roller'

Using host libthread_db library "/lib/libthread_db.so.1".
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1224264016 (LWP 18666)]
[New Thread -1245135968 (LWP 18667)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 67385

Thread 1 (Thread -1224264016 (LWP 18666))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 784
  • #3 <signal handler called>
  • #4 fr_process_set_continue_func
    at fr-process.c line 398
  • #5 window_archive_extract__common
    at window.c line 4796
  • #6 extract_cb
    at dlg-extract.c line 320
  • #7 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #8 IA__g_closure_invoke
    at gclosure.c line 490
  • #9 signal_emit_unlocked_R
    at gsignal.c line 2438
  • #10 IA__g_signal_emit_valist
    at gsignal.c line 2197
  • #11 IA__g_signal_emit
    at gsignal.c line 2241
  • #12 IA__gtk_button_clicked
    at gtkbutton.c line 845
  • #13 gtk_real_button_released
    at gtkbutton.c line 1380
  • #14 IA__g_cclosure_marshal_VOID__VOID
    at gmarshal.c line 77
  • #15 g_type_class_meta_marshal
    at gclosure.c line 567
  • #16 IA__g_closure_invoke
    at gclosure.c line 490
  • #17 signal_emit_unlocked_R
    at gsignal.c line 2368
  • #18 IA__g_signal_emit_valist
    at gsignal.c line 2197
  • #19 IA__g_signal_emit
    at gsignal.c line 2241
  • #20 IA__gtk_button_released
    at gtkbutton.c line 837
  • #21 gtk_button_button_release
    at gtkbutton.c line 1273
  • #22 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 83
  • #23 g_type_class_meta_marshal
    at gclosure.c line 567
  • #24 IA__g_closure_invoke
    at gclosure.c line 490
  • #25 signal_emit_unlocked_R
    at gsignal.c line 2476
  • #26 IA__g_signal_emit_valist
    at gsignal.c line 2207
  • #27 IA__g_signal_emit
    at gsignal.c line 2241
  • #28 gtk_widget_event_internal
    at gtkwidget.c line 3732
  • #29 IA__gtk_propagate_event
    at gtkmain.c line 2185
  • #30 IA__gtk_main_do_event
    at gtkmain.c line 1422
  • #31 gdk_event_dispatch
    at gdkevents-x11.c line 2291
  • #32 IA__g_main_context_dispatch
    at gmain.c line 1916
  • #33 g_main_context_iterate
    at gmain.c line 2547
  • #34 IA__g_main_loop_run
    at gmain.c line 2751
  • #35 IA__gtk_main
    at gtkmain.c line 1001
  • #36 main
    at main.c line 220
  • #0 __kernel_vsyscall 


Other information:
in frame #4, fr_proc != NULL, but fr_proc->current_comm is -1 , so
fr_proc->comm[-1] returns garbage i guess.
Comment 1 Marinus Schraal 2006-04-02 11:20:07 UTC 
Note that I can reproduce this with .tar.gz & tar.bz2 , but not with .zip files.
Comment 2 Christian Kirbach 2006-04-02 14:59:03 UTC 
unique and good trace, confirming
Comment 3 Paolo Bacchilega 2006-04-04 11:26:06 UTC 
fixed in current CVS, thanks.