Hi, For years I have run a weekly perl script that checks the integrity of some files (md5checksum comparisons), and then mails me a reassuring message. Today I got the following error message: *** Error in `/usr/bin/perl': double free or corruption (!prev): 0x000000000209fdd0 *** ======= Backtrace: ========= /lib64/libc.so.6(+0x7abf6)[0x7f35724efbf6] /lib64/libc.so.6(+0x7b973)[0x7f35724f0973] /usr/bin/perl(Perl_av_extend+0x1ed)[0x49ce5d] /usr/bin/perl(Perl_stack_grow+0x22)[0x4d2d72] /usr/bin/perl(Perl_pp_gv+0x24)[0x49f654] /usr/bin/perl(Perl_runops_standard+0x16)[0x49ee16] /usr/bin/perl(perl_run+0x402)[0x43cbb2] /usr/bin/perl(main+0x11b)[0x41ec5b] /lib64/libc.so.6(__libc_start_main+0xf5)[0x7f3572496a15] /usr/bin/perl[0x41ec95] ======= Memory map: ======== 00400000-00571000 r-xp 00000000 08:07 10853 /usr/bin/perl 00770000-00771000 r--p 00170000 08:07 10853 /usr/bin/perl 00771000-00776000 rw-p 00171000 08:07 10853 /usr/bin/perl 017cf000-0245d000 rw-p 00000000 00:00 0 [heap] 7f3572058000-7f357206d000 r-xp 00000000 08:07 785018 /lib64/libgcc_s.so.1 7f357206d000-7f357226c000 ---p 00015000 08:07 785018 /lib64/libgcc_s.so.1 7f357226c000-7f357226d000 r--p 00014000 08:07 785018 /lib64/libgcc_s.so.1 7f357226d000-7f357226e000 rw-p 00015000 08:07 785018 /lib64/libgcc_s.so.1 7f357226e000-7f3572274000 r-xp 00000000 08:07 1839943 /usr/lib/perl5/5.16.2/x86_64-linux-thread-multi/auto/File/Glob/Glob.so 7f3572274000-7f3572473000 ---p 00006000 08:07 1839943 /usr/lib/perl5/5.16.2/x86_64-linux-thread-multi/auto/File/Glob/Glob.so 7f3572473000-7f3572474000 r--p 00005000 08:07 1839943 /usr/lib/perl5/5.16.2/x86_64-linux-thread-multi/auto/File/Glob/Glob.so 7f3572474000-7f3572475000 rw-p 00006000 08:07 1839943 /usr/lib/perl5/5.16.2/x86_64-linux-thread-multi/auto/File/Glob/Glob.so 7f3572475000-7f3572618000 r-xp 00000000 08:07 784908 /lib64/libc-2.17.so 7f3572618000-7f3572818000 ---p 001a3000 08:07 784908 /lib64/libc-2.17.so 7f3572818000-7f357281c000 r--p 001a3000 08:07 784908 /lib64/libc-2.17.so 7f357281c000-7f357281e000 rw-p 001a7000 08:07 784908 /lib64/libc-2.17.so 7f357281e000-7f3572822000 rw-p 00000000 00:00 0 7f3572822000-7f3572839000 r-xp 00000000 08:07 784934 /lib64/libpthread-2.17.so 7f3572839000-7f3572a38000 ---p 00017000 08:07 784934 /lib64/libpthread-2.17.so 7f3572a38000-7f3572a39000 r--p 00016000 08:07 784934 /lib64/libpthread-2.17.so 7f3572a39000-7f3572a3a000 rw-p 00017000 08:07 784934 /lib64/libpthread-2.17.so 7f3572a3a000-7f3572a3e000 rw-p 00000000 00:00 0 7f3572a3e000-7f3572a4a000 r-xp 00000000 08:07 784912 /lib64/libcrypt-2.17.so 7f3572a4a000-7f3572c4a000 ---p 0000c000 08:07 784912 /lib64/libcrypt-2.17.so 7f3572c4a000-7f3572c4b000 r--p 0000c000 08:07 784912 /lib64/libcrypt-2.17.so 7f3572c4b000-7f3572c4c000 rw-p 0000d000 08:07 784912 /lib64/libcrypt-2.17.so 7f3572c4c000-7f3572c7a000 rw-p 00000000 00:00 0 7f3572c7a000-7f3572c7d000 r-xp 00000000 08:07 784914 /lib64/libdl-2.17.so 7f3572c7d000-7f3572e7c000 ---p 00003000 08:07 784914 /lib64/libdl-2.17.so 7f3572e7c000-7f3572e7d000 r--p 00002000 08:07 784914 /lib64/libdl-2.17.so 7f3572e7d000-7f3572e7e000 rw-p 00003000 08:07 784914 /lib64/libdl-2.17.so 7f3572e7e000-7f3572f7b000 r-xp 00000000 08:07 784916 /lib64/libm-2.17.so 7f3572f7b000-7f357317a000 ---p 000fd000 08:07 784916 /lib64/libm-2.17.so 7f357317a000-7f357317b000 r--p 000fc000 08:07 784916 /lib64/libm-2.17.so 7f357317b000-7f357317c000 rw-p 000fd000 08:07 784916 /lib64/libm-2.17.so 7f357317c000-7f357319d000 r-xp 00000000 08:07 784901 /lib64/ld-2.17.so 7f3573379000-7f357337d000 rw-p 00000000 00:00 0 7f357339b000-7f357339d000 rw-p 00000000 00:00 0 7f357339d000-7f357339e000 r--p 00021000 08:07 784901 /lib64/ld-2.17.so 7f357339e000-7f357339f000 rw-p 00022000 08:07 784901 /lib64/ld-2.17.so 7f357339f000-7f35733a0000 rw-p 00000000 00:00 0 7ffff3607000-7ffff3628000 rw-p 00000000 00:00 0 [stack] 7ffff371c000-7ffff371d000 r-xp 00000000 00:00 0 [vdso] ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall] The script hasn't changed, so it must be due to a recent 'upgrade' to perl. /lib64/libc.so.6 is a symlink to libc-2.17.so which is also in /lib64/ Where should I start trying to solve this problem? Bob -- Bob Williams System: Linux 3.7.10-1.1-desktop Distro: openSUSE 12.3 (x86_64) with KDE Development Platform: 4.10.1 "release 545" Uptime: 06:00am up 1 day 16:20, 3 users, load average: 0.24, 0.14, 0.14 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org