mirror of
https://github.com/RIOT-OS/RIOT.git
synced 2024-12-29 04:50:03 +01:00
76 lines
2.1 KiB
Plaintext
76 lines
2.1 KiB
Plaintext
VALGRIND SUPPORT
|
|
================
|
|
|
|
If you want to use valgrind, you should recompile native with either
|
|
HAVE_VALGRIND_H or HAVE_VALGRIND_VALGRIND_H depending on the location
|
|
of the valgrind header (i.e. <valgrind.h> or <valgrind/valgrind.h>)
|
|
like this:
|
|
|
|
CFLAGS="-DHAVE_VALGRIND_VALGRIND_H" make
|
|
|
|
That way native can tell valgrind about RIOTs stacks and prevent
|
|
valgrind from reporting lots of false positives.
|
|
|
|
Usage:
|
|
Simply pass the ordinary command to valgrind like this:
|
|
|
|
valgrind ./bin/RIOT.elf tap0
|
|
|
|
This will yield some information whenever valgrind detects an invalid
|
|
memory access.
|
|
|
|
In order to debug the program when this occurs you can pass the
|
|
--db-attach parameter to valgrind like this:
|
|
|
|
valgrind --db-attach=yes ./bin/RIOT.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
|
|
|
|
|
|
NETWORK SUPPORT
|
|
===============
|
|
|
|
If you compile RIOT for the native cpu and include the native_net
|
|
module, you need to specify a network interface like this:
|
|
|
|
./bin/default-native.elf tap0
|
|
|
|
|
|
SETTING UP A TAP NETWORK
|
|
========================
|
|
|
|
There is a shellscript in RIOT/cpu/native called tapsetup.sh 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:
|
|
|
|
./tapsetup.sh create [count]
|
|
|
|
To delete the bridge and all tap interfaces:
|
|
|
|
./tapsetup.sh delete
|
|
|
|
|
|
OSX TAP NETWORKING
|
|
==================
|
|
|
|
For tun/tap networking in OSX you will need:
|
|
http://tuntaposx.sourceforge.net/
|
|
|
|
For OSX there is a seperate script called tapsetup-osx.sh.
|
|
Run it, (it instructs you to start the RIOT instances).
|
|
In contrast to linux you will need to run 'tapsetup-osx.sh delete'
|
|
after killing your instances and rerun 'tapsetup-osx.sh create' before
|
|
restarting.
|
|
Packet delivery under OSX only works with user assistance at the
|
|
moment. run 'kill -SIGIO <RIOT process ID>' to deliver a packet to a
|
|
specific RIOT instance.
|