https://bugs.kde.org/show_bug.cgi?id=356457

            Bug ID: 356457
           Summary: valgrind: m_mallocfree.c:2042 (vgPlain_arena_free):
                    Assertion 'blockSane(a, b)' failed.
           Product: valgrind
           Version: unspecified
          Platform: Compiled Sources
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: jsew...@acm.org
          Reporter: joost.vandevond...@mat.ethz.ch

Our nightly tester runs a few thousand testcases, and usually this goes all
fine. However, seemingly some rare condition can trigger the following assert:

==10071== Memcheck, a memory error detector
==10071== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==10071== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==10071== Command:
/data/schuetto/auto_regtesting/regtests/cp2k/exe/local_valgrind/cp2k.sdbg
O-B97-q6.inp
==10071== 
blockSane: fail -- redzone-hi

valgrind: m_mallocfree.c:2042 (vgPlain_arena_free): Assertion 'blockSane(a, b)'
failed.

host stacktrace:
==10071==    at 0x38083F48: show_sched_status_wrk (m_libcassert.c:343)
==10071==    by 0x38084064: report_and_quit (m_libcassert.c:415)
==10071==    by 0x380841F1: vgPlain_assert_fail (m_libcassert.c:481)
==10071==    by 0x380925E6: vgPlain_arena_free (m_mallocfree.c:2042)
==10071==    by 0x3811B51E: vgModuleLocal_img_done (image.c:778)
==10071==    by 0x380BAFF0: vgModuleLocal_read_elf_debug_info (readelf.c:3027)
==10071==    by 0x380B343A: di_notify_ACHIEVE_ACCEPT_STATE (debuginfo.c:749)
==10071==    by 0x380B343A: vgPlain_di_notify_mmap (debuginfo.c:1067)
==10071==    by 0x380D963D: vgModuleLocal_generic_PRE_sys_mmap
(syswrap-generic.c:2367)
==10071==    by 0x3810D6A1: vgSysWrap_amd64_linux_sys_mmap_before
(syswrap-amd64-linux.c:637)
==10071==    by 0x380D60A4: vgPlain_client_syscall (syswrap-main.c:1905)
==10071==    by 0x380D2B9A: handle_syscall (scheduler.c:1118)
==10071==    by 0x380D424E: vgPlain_scheduler (scheduler.c:1435)
==10071==    by 0x380E37B6: thread_wrapper (syswrap-linux.c:102)
==10071==    by 0x380E37B6: run_a_thread_NORETURN (syswrap-linux.c:155)

sched status:
  running_tid=1

Thread 1: status = VgTs_Runnable (lwpid 10071)
==10071==    at 0x3232A1761A: mmap (in /lib64/ld-2.12.so)
==10071==    by 0x3232A076B9: _dl_map_object_from_fd (in /lib64/ld-2.12.so)
==10071==    by 0x3232A08399: _dl_map_object (in /lib64/ld-2.12.so)
==10071==    by 0x3232A0C3A1: openaux (in /lib64/ld-2.12.so)
==10071==    by 0x3232A0E285: _dl_catch_error (in /lib64/ld-2.12.so)
==10071==    by 0x3232A0CA84: _dl_map_object_deps (in /lib64/ld-2.12.so)
==10071==    by 0x3232A0330F: dl_main (in /lib64/ld-2.12.so)
==10071==    by 0x3232A160AD: _dl_sysdep_start (in /lib64/ld-2.12.so)
==10071==    by 0x3232A014A3: _dl_start (in /lib64/ld-2.12.so)
==10071==    by 0x3232A00B07: ??? (in /lib64/ld-2.12.so)
==10071==    by 0x1: ???
==10071==    by 0xFFF000A32: ???
==10071==    by 0xFFF000A7C: ???


Note: see also the FAQ in the source distribution.

I have attempted to reproduce this (running exactly the same commands and
binary, etc.) but this didn't fail. The error appears to happen before our
executable is really running, so maybe something is wrong on startup ?

Reproducible: Couldn't Reproduce

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to