Hello, On Sun, 18 Aug 2013 10:23:17 +0200 wwp <subscript free fr> wrote:
Hello there,
I've given mc 4.8.9 a try, compiled from the sources on a 64-bit
CentOS6: it eats memory and CPU at start-up, until it got killed
by either me or kernel. Same with 4.8.10. Back to 4.8.8 and it's fine.
I tried w/ a brand new user (no ~/.mc or ~/.config/mc), same issue.
Any idea what could be wrong either in mc or here?
FYI:
Configuration:
Source code location: .
Compiler: gcc -std=gnu99
Compiler flags: -fdiagnostics-show-option -Wcomment -Wdeclaration-after-statement
-Wfloat-equal -Wformat -Wformat-security -Wimplicit -Wignored-qualifiers -Wmissing-braces
-Wmissing-declarations -Wmissing-parameter-type -Wmissing-prototypes -Wnested-externs -Wno-long-long
-Wno-unreachable-code -Wparentheses -Wpointer-sign -Wreturn-type -Wsequence-point -Wshadow -Wsign-compare
-Wswitch -Wtype-limits -Wuninitialized -Wunused-but-set-variable -Wunused-function -Wunused-label
-Wunused-parameter -Wunused-value -Wunused-variable -Wwrite-strings -O2 -g
File system: Midnight Commander Virtual Filesystem
cpio, tar, sfs, extfs, ftp, fish, smb
Screen library:
Mouse support: gpm and xterm
X11 events support: yes
With subshell support: yes
With background operations: yes
Internal editor: yes
Diff viewer: yes
Support for charset: yes
Search type: glib-regexp
CentOS 6 up-to-date:
gcc-4.4.7-3.el6.x86_64
libstdc++-4.4.7-3.el6.x86_64
glib-1.2.10-33.el6.rf.x86_64
kernel 2.6.32-358.14.1.el6.x86_64
Hm, a bit of investigation and it appears that breaking mc from within gdb gives: (gdb) bt #0 0x000000319cf34c84 in __strncpy_ssse3 () from /lib64/libc.so.6 #1 0x000000319e65a9ba in g_strndup () from /lib64/libglib-2.0.so.0 #2 0x000000319e65abe6 in g_ascii_strup () from /lib64/libglib-2.0.so.0 #3 0x00000000004509bf in str_detect_termencoding () at strutil.c:331 #4 0x0000000000450b4d in str_init_strings (termenc=0x0) at strutil.c:378 #5 0x000000000040e806 in main (argc=1, argv=0x7fffffffe358) at main.c:255 Another interesting point is that compiling mc 4.8.8 from the sources shows the *exact same problem*. It only works when I get the mc binary back from a backup. So it's not mc being broken since 4.8.9, but my system being broken meanwhile? Regards, -- wwp
Attachment:
signature.asc
Description: PGP signature