-
Notifications
You must be signed in to change notification settings - Fork 2.1k
gnrc: crash with (excessive) traffic in native #6123
Copy link
Copy link
Closed
Labels
Area: networkArea: NetworkingArea: NetworkingPlatform: nativePlatform: This PR/issue effects the native platformPlatform: This PR/issue effects the native platformType: bugThe issue reports a bug / The PR fixes a bug (including spelling errors)The issue reports a bug / The PR fixes a bug (including spelling errors)
Description
#2071 seems to have fixed native interrupt handling. But I can still crash a riot native instance by flood pinging.
Steps to reproduce:
- run gnrc_networking
- start a couple (5-10)
ping -f <riot-ip>%tap0 - wait some minutes
Sometimes it takes 30sec, sometimes 5min, but riot reliably crashes.
The problem seems somewhere in gnrc, as my other stack runs fine since #2071 is merged.
Here's a backtrace:
Program received signal SIGSEGV, Segmentation fault.
0x0804df49 in gnrc_pktbuf_start_write ()
(gdb) bt
#0 0x0804df49 in gnrc_pktbuf_start_write ()
#1 0x0805c0ae in _send ()
#2 0x0805ba21 in _event_loop ()
#3 0xf7dba58b in makecontext () from /usr/lib32/libc.so.6
#4 0x00000000 in ?? ()
(gdb)
Edit: summary of reasons why this might not be a GNRC issue in #6123 (comment).
Reactions are currently unavailable
Metadata
Metadata
Labels
Area: networkArea: NetworkingArea: NetworkingPlatform: nativePlatform: This PR/issue effects the native platformPlatform: This PR/issue effects the native platformType: bugThe issue reports a bug / The PR fixes a bug (including spelling errors)The issue reports a bug / The PR fixes a bug (including spelling errors)