Hi.
I am trying to use exp-ptrcheck for the first time. However, the process
terminates and when I check the logs, I get the following errors(below). I
used the tool with default options. However, there is no such problem seen
when I run the memcheck tool on the same code base.
My code binaries are i686 running on x86_64 m/c. The valgind is compiled
with primar platform as x86-linux.
Any help/patch/solution would be of a great help.
Thanks and Regards,
Gyanesh
============================== Errors/Logs==============================
*sysno == 259*
exp-ptrcheck: the 'impossible' happened:
unhandled syscall
==26897== at 0x38014A1D: report_and_quit (m_libcassert.c:193)
==26897== by 0x38014A76: panic (m_libcassert.c:277)
==26897== by 0x38014AAF: vgPlain_tool_panic (m_libcassert.c:292)
==26897== by 0x380028EE: h_post_syscall (h_main.c:2600)
==26897== by 0x3805821C: vgPlain_post_syscall (syswrap-main.c:1729)
==26897== by 0x38058E63: vgPlain_client_syscall (syswrap-main.c:1627)
==26897== by 0x38055982: handle_syscall (scheduler.c:895)
==26897== by 0x38056AA6: vgPlain_scheduler (scheduler.c:1091)
==26897== by 0x380841A4: run_a_thread_NORETURN (syswrap-linux.c:94)
sched status:
running_tid=1
Thread 1: status = VgTs_Runnable
==26897== at 0x937455: timer_create (in /lib/librt-2.5.so)
==26897== by 0x15D83586: OSWrap::Timer::Timer(char const*)
(OSWTimer.C:30)
==26897== by 0x8154FE8:
OSWrap::AttachedTimer<NmaTimer<OBSAI::LargeRP1MsgFileMgr>
>::AttachedTimer(NmaTimer<OBSAI::LargeRP1MsgFileMgr>&, int
(NmaTimer<OBSAI::LargeRP1MsgFileMgr>::*)(), char const*) (OSWTimer.H:128)
==26897== by 0x8154F74:
NmaTimer<OBSAI::LargeRP1MsgFileMgr>::NmaTimer(OBSAI::LargeRP1MsgFileMgr&,
int (OBSAI::LargeRP1MsgFileMgr::*)(), std::string) (NmaTimer.h:167)
==26897== by 0x8154E9A: OBSAI::LargeRP1MsgFileMgr::LargeRP1MsgFileMgr()
(ObsaiCmRequest.h:60)
==26897== by 0x81536B6: __static_initialization_and_destruction_0(int,
int) (ObsaiCmRequest.cpp:16)
==26897== by 0x81537C2: global constructors keyed to
_ZN5OBSAI9CmRequest20m_LargeRP1MsgFileMgrE (ObsaiCmRequest.cpp:402)
==26897== by 0x85BBA35: ??? (in
/vob/do_store/wmx/Linux-i686/image/bin/Nma)
==26897== by 0x80CB4DC: ??? (in
/vob/do_store/wmx/Linux-i686/image/bin/Nma)
==26897== by 0x85BB9A9: __libc_csu_init (in
/vob/do_store/wmx/Linux-i686/image/bin/Nma)
==26897== by 0x7E9E30: (below main) (in /lib/libc-2.5.so)
Thread 2: status = VgTs_WaitSys
==26897== at 0x89E211: ??? (in /lib/libc-2.5.so)
==26897== by 0x91F49A: start_thread (in /lib/libpthread-2.5.so)
==26897== by 0x8A542D: clone (in /lib/libc-2.5.so)
Thread 3: status = VgTs_WaitSys
==26897== at 0x9384F8: timer_helper_thread (in /lib/librt-2.5.so)
==26897== by 0x91F49A: start_thread (in /lib/libpthread-2.5.so)
==26897== by 0x8A542D: clone (in /lib/libc-2.5.so)
------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its
next-generation tools to help Windows* and Linux* C/C++ and Fortran
developers boost performance applications - including clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
