Problem Description ====================== Analyze memory leak in the lemon_server with valgrind for qemuppc failed: run_innerloop detected host state invariant failure Expected Behavior ====================== Analyze memory leak in the lemon_server with valgrind for qemuppc should successfully Observed Behavior ====================== # valgrind --leak-check=full --show-reachable=yes lemon_server ==226== Memcheck, a memory error detector ==226== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==226== Using Valgrind-3.9.0 and LibVEX; rerun with -h for copyright info ==226== Command: lemon_server ==226== valgrind: /build_1211/qemuppc/bitbake_build/tmp/work/ppc7400-wrs- linux/valgrind/3.9.0-r8/valgrind-3.9.0/coregrind/m_scheduler/scheduler.c:1513 (vgPlain_scheduler): the 'impossible' happened. valgrind: VG_(scheduler), phase 3: run_innerloop detected host state invariant failure ==226== at 0x380B7604: report_and_quit (m_libcassert.c:260) ==226== by 0x380B7783: vgPlain_assert_fail (m_libcassert.c:340) ==226== by 0x381122B3: vgPlain_scheduler (scheduler.c:1511) ==226== by 0x38127A1F: run_a_thread_NORETURN (syswrap-linux.c:103) sched status: running_tid=1 Thread 1: status = VgTs_Runnable ==226== at 0xFFC5BF0: _dl_start (rtld.c:339) Logs ====================== see attachment
step 1: build && make project: /path/to/wrlinux-7/wrlinux/configure --enable-board=qemuppc --enable-kernel=standard --enable-rootfs=glibc-small+debug+analysis+gdb+usttrace_demo+valgrind --with-layer=examples/lemon_layer --enable-build=profiling && make fs && make fs-debug step 2:Boot the target. TARGET_QEMU_HTTP_REPORT=tcp:8000:8000 make start-target TOPTS="-t -in 1" setp 3: Create a new connection. Name: Lemon Demo QEMUX8 Target Address: 192.168.201.15 Platform Project : qemuppc step 4: Analyze memory leak in the lemon_server with valgrind valgrind --leak-check=full --show-reachable=yes lemon_server
