With native this isn't really that easy to reproduce, since the TAP interface is able to handle the load quite fast (it even swallowed

for _ in $(seq 10); do sudo ping6 fe80::b41f:ceff:febe:78d3%tapbr0 -s1452 -i0 -c 100000 & done

or

for _ in $(seq 10); do sudo ping6 fe80::b41f:ceff:febe:78d3%tapbr0 -s1452 -f -c 100000 & done

mostly without problems). So I can't really test. However

Please provide a backport to the 2019.01-branch (You can use the script in #8968 for that if you want to).

@miri64

With native this isn't really that easy to reproduce, since the TAP interface is able to handle the load quite fast (it even swallowed ...

When bombarding examples/gnrc_networking on native using

sudo ping6 fe80::280d:21ff:fed1:c5ed -Itap0 -s1392 -i 0

in 4 terminals, it crashes with

> examples/gnrc_networking/../../Makefile.include:540: recipe for target 'term' failed
make: *** [term] segmentation violation (core dumped)

Where can I find the core file to take a look why it crashed?

Where can I find the core file to take a look why it crashed?

I had the same question for a while. On systemd systems, it is probably in /var/lib/systemd/coredump. Otherwise, /proc/sys/kernel/core_pattern might give a hint.

why it crashed

I usually compile native with CFLAGS += -g, then run it within gdb. On crash, get a backtrace with "bt".

I had the same question for a while. On systemd systems, it is probably in /var/lib/systemd/coredump. Otherwise, /proc/sys/kernel/core_pattern might give a hint.

Thanks. I'm using UNIX/Linux since 25 years, systemd is a hell. In the past it was so easy, the core file was simply created in the current directory.