Summary: | TCPICK segfaults out when there's traffic | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Chris Chance <cchance> |
Component: | Current packages | Assignee: | AMD64 Project <amd64> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Chris Chance
2005-05-10 10:43:35 UTC
phi / # tcpick -i eth0 Starting tcpick 0.2.1 at 2005-05-15 23:44 CEST Timeout for connections is 600 tcpick: listening on eth0 485 packets captured 0 tcp sessions detected Not reproducible on my system. ATs, please test on a stable system. Well not much i can add besides the strace... that i did ... only difference i can think of is the fact my pc is handling close to 1000pps Ok, then let's go an debug it properly :-) Please run this: FEATURES="nostrip" CFLAGS="-O0 -ggdb -g3" CXXFLAGS="-O0 -ggdb -g3" emerge net-analyzer/tcpick After that: ulimit -c unlimited # allows core dumps to be dropped gdb tcpick # starts gdb and type in: run -i eth0 # runs tcpick inside gdb In case of a segfault, tcpcik will dump a "core" file. Please attach this to the Bug. Further, when running tcpick in gdb, a segfault will throw you back into gdb console. When this happens, just type in bt and add the output here. Please reopen this BUG when you attach additional info. |