New answers tagged debugging
The strace command lists the systemcalls the application make as it is running. If you're not de developer: Section 2 of the system manual documents systemcalls helping you understand what is happening. man 2 poll DESCRIPTION poll() performs a similar task to select(2): it waits for one of a set of file descriptors to become ready to perform ...
just had the same problem. In my case this was a network misconfiguration. server was configured with 10.0.1.111 255.255.254.0 and client was configured with 10.0.0.15 255.255.255.0. Changing the netmask on client side to /23 solved my problem. hope this could help. regards tcpdump
I had the same problem. After some searching I found this page which suggest that this caused by a race condition. Although the workaround given there wasn't applicable for me, after stopping every other debugging process (Visual Studio) these annoying error messages didn't show up anymore.
Given an unstripped vmlinux with debugging symbols (typically included with "linux-devel" or "linux-headers" packages matching your kernel version), you can use the addr2line program included with binutils to translate addresses to lines in source files. Consider this call trace: Call Trace: [<ffffffff8107bf5d>] ? finish_task_switch+0x3d/0x120 ...
I don't have a ~= RHEL5 at hand, so the output shown is from a Fedora 20, though the process should be mostly the same (the name of the function has changed). You'd need to install the appropriate kernel-debug-debuginfo package for your kernel (assuming RHEL or derivative distro). This package provides a vmlinux image (an uncompressed not stripped version ...
Top 50 recent answers are included