Hi:
There is valgrind assert failure when valgrind run the process.
But it does not always occurred ,sometimes.
There is only two thread , One the thread is sleeping and
waiting the message, another thread is running.
I do not how to debug it, can you show me some idea?
Is there any flags of valgrind output to help me debug or
trace the assertion failure.
The output as below:
--8330-- sync signal handler: signal=11, si_code=1, EIP=0x5c670cd,
eip=0x834dc4fc, from kernel
--8330-- SIGSEGV: si_code=1 faultaddr=0xfedfbb04 tid=1 ESP=0xfedfbb04
seg=0xfe5ff000-0xfedfbfff
--8330-- -> extended stack base to 0xfedfb000
--8330-- sync signal handler: signal=11, si_code=1, EIP=0x5c23ce1,
eip=0x833e782c, from kernel
--8330-- SIGSEGV: si_code=1 faultaddr=0xfedfae44 tid=1 ESP=0xfedfae44
seg=0xfe5ff000-0xfedfafff
--8330-- -> extended stack base to 0xfedfa000
--8330-- sync signal handler: signal=11, si_code=2, EIP=0x5dc84bf,
eip=0x835f0014, from kernel
--8330-- SIGSEGV: si_code=2 faultaddr=0x5dc8ce8 tid=1 ESP=0xfedfac50
seg=0x5c0a000-0x5e37fff
--8330-- delivering signal 11 (SIGSEGV):2 to thread 1
--8330-- delivering 11 (code 2) to default handler; action: terminate+core
--8330-- -> extended stack base to 0xfedfa000
--8330-- get_thread_out_of_syscall zaps tid 2 lwp 8331
--8330-- sys_sigaction: sigNo 11, new 0x8326deec, old 0x0, new flags 0x0
--8330-- sys_sigaction: sigNo 7, new 0x8326deec, old 0x0, new flags 0x0
--8330-- sys_sigaction: sigNo 4, new 0x8326deec, old 0x0, new flags 0x0
--8330-- sys_sigaction: sigNo 8, new 0x8326deec, old 0x0, new flags 0x0
valgrind: external/valgrind/coregrind/m_scheduler/scheduler.c:2240
(vgPlain_sanity_check_general): Assertion
'VG_TDICT_CALL(tool_expensive_sanity_check)' failed.
host stacktrace:
==8330== at 0x3804793C: show_sched_status_wrk (m_libcassert.c:343)
sched status:
running_tid=1
Note: see also the FAQ in the source distribution.
It contains workarounds to several common problems.
In particular, if Valgrind aborted or crashed after
identifying problems in your program, there's a good chance
that fixing those problems will prevent Valgrind aborting or
crashing, especially if it happened in m_mallocfree.c.
Env:
Version: 3.12.
CPU : Aarch64
ABI: armeabi-v7a
OS: android
BR
Owen
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
