wcmcommander work normal, but crash with core file, when copy/move file or folder. admin@vladiom:~ % gdb wcm GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"...(no debugging symbols found)... (gdb) (gdb) run Starting program: /usr/local/bin/wcm (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[New LWP 102011] [New Thread 810e16000 (LWP 102011/wcm)] [New Thread 810e17e00 (LWP 100139/wcm)] Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 810e16000 (LWP 102011/wcm)] 0x000000000045bbd9 in ?? () Current language: auto; currently minimal (gdb) (gdb) q The program is running. Exit anyway? (y or n) y admin@vladiom:~ % When I used wcm on FreeBSD 10.3, there were no such problems. admin@vladiom:~ % pkg version -v | grep wcm wcmcommander-0.20.0_4 = up-to-date with index admin@vladiom:~ % uname -srm FreeBSD 11.0-RELEASE-p10 amd64
Cannot reproduce, please provide a backtrace. You may need rebuilding wcm WITH_DEBUG first.
Created attachment 183527 [details] backtrace log (In reply to Dmitry Marakasov from comment #1) Something else?
(In reply to Vladimir Omelchuk from comment #2) > Created attachment 183527 [details] > backtrace log > > (In reply to Dmitry Marakasov from comment #1) > > Something else? Hmm, I still don't see an apparent cause. The code is smelly, but it looks correct. Could you maybe print the contents of second argument of AddFieldTextToHistory() ("frame 1, print Txt" should work)? Could you also provide details on you environment (env, locale, make.conf), and the conditions to reproduce the bug (is it always reproducible? or only with cyrillic names?)
Created attachment 183552 [details] backtrace log with env, locale, make.conf (In reply to Dmitry Marakasov from comment #3) > Could you also provide details on you environment (env, locale, make.conf) Done. > and the conditions to reproduce the bug (is it always reproducible? or only with cyrillic names?) Yes, always.
Is this still a problem? I couldn't reproduce it after all.
Created attachment 202812 [details] core file (In reply to Dmitry Marakasov from comment #5) Dmitry, hi! Yes, this problem is still present! :( Core file in the attachment ... May be this help understand problem ...
(In reply to Vladimir Omelchuk from comment #6) > Core file in the attachment ... Core from different binary is not useful. A reliable way to reproduce the problem is needed. Anyway, I've dropped maintainership of this port. The upstream seem to be dead too.