|
From: Julian S. <js...@ac...> - 2006-01-12 17:59:44
|
> ==2272== Warning: set address range perms: large range 4294960294, a 0, v 0 > > Memcheck: mc_main.c:584 (set_address_range_perms): the 'impossible' > happened. ==2272== at 0x70015010: report_and_quit (m_libcassert.c:136) > ==2272== by 0x70015260: vgPlain_assert_fail (m_libcassert.c:199) > ==2272== by 0x70003E7C: set_address_range_perms (mc_main.c:573) > ==2272== by 0x7004E448: vgSysWrap_generic_sys_read_after > (priv_types_n_macros.h:249) > ==2272== by 0x7005236C: vgPlain_post_syscall (syswrap-main.c:934) > ==2272== by 0x7005213C: vgPlain_client_syscall (syswrap-main.c:860) > ==2272== by 0x7003D268: handle_syscall (scheduler.c:624) > ==2272== by 0x7003D670: vgPlain_scheduler (scheduler.c:725) > ==2272== by 0x700533E0: thread_wrapper (syswrap-linux.c:86) > ==2272== by 0x70053514: run_a_thread_NORETURN (syswrap-linux.c:119) > ==2272== by 0x70053664: vgModuleLocal_start_thread_NORETURN Well, umm. The problem is certainly syscall related, but this stack trace lacks the critical frame which would indicate which syscall it is. (What was really called from syswrap-main.c:934?) Can you rerun with --trace-syscalls=yes. This should give an strace-style log of syscalls. Just send the couple of lines prior to the "Warning" line. J |