|cbaeccdb90||8 years ago|
|include||8 years ago|
|netdev2_tap||8 years ago|
|periph||8 years ago|
|Makefile||8 years ago|
|Makefile.include||8 years ago|
|README.md||8 years ago|
|irq_cpu.c||8 years ago|
|lpm_cpu.c||8 years ago|
|native_cpu.c||8 years ago|
|panic.c||8 years ago|
|startup.c||8 years ago|
|syscalls.c||8 years ago|
|tramp.S||8 years ago|
Rebuild your application using the all-valgrind target like this:
make -B clean all-valgrind
That way native will tell Valgrind about RIOT's stacks and prevent
Valgrind from reporting lots of false positives.
The debug information flag
-g is not strictly necessary, but passing
it allows Valgrind to tell you precisely which code triggered the error.
To run your application run:
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:
valgrind --db-attach=yes ./bin/native/default.elf tap0
Now, you will be asked whether you would like to attach the running process to gdb whenever a problem occurs.
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
If you compile RIOT for the native cpu and include the
module, you need to specify a network interface like this:
make term PORT=tap0
Setting Up A Tap Network
There is a shellscript in RIOT/dist/tools/tapsetup called
tapsetup which you
can use to create a network of tap interfaces.
Usage: To create a bridge and two (or count at your option) tap interfaces:
../../dist/tools/tapsetup/tapsetup [-c [<count>]]
On OSX you need to start the RIOT instance at some point during the script's execution. The script will instruct you when to do that.
To delete the bridge and all tap interfaces:
For OSX you have to run this after killing your RIOT instance and rerun
../../dist/tools/tapsetup [-c [<count>]] before restarting.
You can daemonize a riot process. This is useful for larger networks. Valgrind will fork along with the riot process and dump its output in the terminal.
Compile Time Options
to exit the riot core after the last thread has exited.