Red Hat Bugzilla – Bug 983937
[abrt] filezilla-188.8.131.52-1.fc18: __pthread_mutex_lock: Process /usr/bin/filezilla was killed by signal 11 (SIGSEGV)
Last modified: 2013-10-16 05:45:13 EDT
Description of problem:
Upload a DIRECTORY to an existing FILE.
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#0 __pthread_mutex_lock at pthread_mutex_lock.c:64
#1 wxMutexInternal::Lock at src/unix/threadpsx.cpp:248
#2 Enter at include/wx/thread.h:271
#3 wxEvtHandler::ProcessPendingEvents at src/common/event.cpp:1174
#4 wxAppConsole::ProcessPendingEvents at src/common/appbase.cpp:294
#5 wxAppBase::ProcessIdle at src/common/appcmn.cpp:435
#6 wxapp_idle_callback at src/gtk/app.cpp:213
#11 gtk_main at gtkmain.c:1257
#12 wxEventLoop::Run at src/gtk/evtloop.cpp:76
#13 wxAppBase::MainLoop at src/common/appcmn.cpp:312
Created attachment 772631 [details]
Created attachment 772632 [details]
Created attachment 772633 [details]
Created attachment 772634 [details]
Created attachment 772635 [details]
Created attachment 772636 [details]
Created attachment 772637 [details]
Created attachment 772638 [details]
Created attachment 772639 [details]
Created attachment 772640 [details]
Please try to reproduce with current filezilla-3.7.3-1.fc18
3.7.3-1 does not crash anymore.
However it neither overwrites the target file nor displays the overwrite option dialog... but it's another story: maybe a feature request.
Many thanks for your work on it.