| Summary: | net-analyzer/ntop-3.2-r2 freezing (race condition?) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Ben Anderson <roothorick> |
| Component: | Current packages | Assignee: | Alin Năstac (RETIRED) <mrness> |
| Status: | RESOLVED TEST-REQUEST | ||
| Severity: | major | CC: | jakub, netmon, stian |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Ben Anderson
2008-01-17 05:50:50 UTC
Tried w/ 3.3? Also might want to try to compile this w/ -O0 instead of -Os. Tested with valgrind? 3.3 has the same problem. Compiling with -O0 reduced it slightly, but it still freezes. What exactly can valgrind do that might help? It can catch one kind of race, a thread starting to use a variable before it is initialized by another one (caught some thread bugs before with it). If you compile it with debuging, and without -O, you can attach gdb to each of the threads when it has frozen and make backtraces /proc/<PID>/task/ shows you all the threads. I've became the maintainer of ntop. Reassigned its bugs to me. Please test ntop-3.3.6. Closed as TEST-REQUEST. |