Bug 118010 - valgrind crashes with assertion: aspacemgr.c:1058 (vgPlain_pad_address_space): Assertion '!ret.isError' failed.
Summary: valgrind crashes with assertion: aspacemgr.c:1058 (vgPlain_pad_address_space)...
Status: RESOLVED FIXED
Alias: None
Product: valgrind
Classification: Developer tools
Component: general (other bugs)
Version First Reported In: 3.0.1
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-09 14:51 UTC by Lukasz
Modified: 2023-05-24 11:51 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Lukasz 2005-12-09 14:51:52 UTC 
I was trying to execute my project using valgrind and this is what I got:

valgrind: aspacemgr.c:1058 (vgPlain_pad_address_space): Assertion '!ret.isError'
failed.
==20644==    at 0xB001693E: panic (m_libcassert.c:175)
==20644==    by 0xB001693D: vgPlain_assert_fail (m_libcassert.c:169)
==20644==    by 0xB003BC7B: vgPlain_pad_address_space (aspacemgr.c:1058)
==20644==    by 0xB005132C: vgSysWrap_linux_sys_io_setup_before
(syswrap-linux.c:699)
==20644==    by 0xB004EAC1: vgPlain_client_syscall (syswrap-main.c:622)
==20644==    by 0xB0038F99: handle_syscall (scheduler.c:589)
==20644==    by 0xB003922E: vgPlain_scheduler (scheduler.c:688)
==20644==    by 0xB004F431: vgModuleLocal_thread_wrapper (syswrap-linux.c:80)
==20644==    by 0xB004B99E: run_a_thread_NORETURN (syswrap-x86-linux.c:150)

I was using debian package distribution with version: valgrind-3.0.1-Debian
Comment 1 Nicholas Nethercote 2005-12-09 17:07:15 UTC 
Can you try with 3.1.0?  The address space management is much more robust 
than in 3.0.1.  Thanks.
Comment 2 Lukasz 2005-12-13 16:27:16 UTC 
It turns out that valgrind 3.1.0 works fine (bug does not show up).
Thanks for quick response.
Comment 3 Tom Hughes 2005-12-13 17:01:36 UTC 
Reopening to correct resolution.
Comment 4 Tom Hughes 2005-12-13 17:01:49 UTC 
*** Bug has been marked as fixed ***.