riot-ci/RIOT
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

native: add debug-valgrind target

Browse Source 
debug-valgrind-server: Starts valgrind as gdb-server (vgdb)
debug-valgrind:        Connects to vgdb
This commit is contained in:
Oleg Hahm 2016-01-26 17:38:15 +01:00
parent cc97fc63ef
commit 2b949fcce1
2 changed files with 20 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
boards/native/Makefile.include
View File

@ -86,6 +86,11 @@ term-valgrind: export VALGRIND_FLAGS ?= \
--track-origins=yes \
--fullpath-after=$(RIOTBASE)/ \
--read-var-info=yes
debug-valgrind-server: export VALGRIND_FLAGS ?= --vgdb=yes --vgdb-error=0 -v \
--leak-check=full --track-origins=yes --fullpath-after=${RIOTBASE} \
--read-var-info=yes
debug-valgrind: export VALGRIND_PID ?= $(shell pgrep -n memcheck-x86-li -u ${USER} | cut -d" " -f1)
debug-valgrind: export DEBUGGER_FLAGS := -ex "target remote | vgdb --pid=${VALGRIND_PID}" $(DEBUGGER_FLAGS)
term-cachegrind: export CACHEGRIND_FLAGS += --tool=cachegrind
term-gprof: export TERMPROG = GMON_OUT_PREFIX=gmon.out $(ELF)
all-valgrind: export CFLAGS += -DHAVE_VALGRIND_H -g
@ -135,11 +140,15 @@ all-valgrind: all
all-cachegrind: all
term-valgrind:
# use this if you want to attach gdb from valgrind:
# echo 0 > /proc/sys/kernel/yama/ptrace_scope
# VALGRIND_FLAGS += --db-attach=yes
$(VALGRIND) $(VALGRIND_FLAGS) $(ELF) $(PORT)
debug-valgrind-server:
$(VALGRIND) $(VALGRIND_FLAGS) $(ELF) $(PORT)
debug-valgrind:
@echo $(VALGRIND_PID)
$(DEBUGGER) $(DEBUGGER_FLAGS)
term-cachegrind:
$(VALGRIND) $(CACHEGRIND_FLAGS) $(ELF) $(PORT)

18
cpu/native/README.md
View File

@ -18,20 +18,18 @@ All this does is run your application under Valgrind.
Now Valgrind will print some information whenever it detects an
invalid memory access.
In order to debug the program when this occurs you can pass the
--db-attach parameter to Valgrind. E.g:
In order to debug the program when this occurs you can use the targets
debug-valgrind-server and debug-valgrind. Therefore, you need to open two
terminals and run:
valgrind --db-attach=yes ./bin/native/default.elf tap0
make debug-valgrind-server
Now, you will be asked whether you would like to attach the running
process to gdb whenever a problem occurs.
in the first one and run:
In order for this to work under Linux 3.4 or newer, you might need to
disable the ptrace access restrictions:
As root call:
echo 0 > /proc/sys/kernel/yama/ptrace_scope
make debug-valgrind
in the seconde one. This starts per default gdb attached to valgrinds gdb
server (vgdb).
Network Support
===============