Hi Sam, I found this problem in the stock upstream 2.6.18.8 kernel, and for me the fix involved the following: 1. apply the attached patch (taken from the RHEL 5 kernel source package) 2. build the kernel with CONFIG_COMPAT_VDSO disabled 3. use an older version of gcc (I had been testing with 6.6; stock 6.4 worked) Without all of those things, I would usually see useless stack traces when attaching to running processes or analyzing core dumps of multithreaded programs. (The original RedHat patch, linux-2.6-misc-fix-vdso-in-core-dumps.patch, does not apply cleanly to a stock kernel, so I've also attached the same patch with conflicts against a stock 2.6.18.8 kernel resolved as fix-vdso-in-core-dumps-rediff.patch.) I'd be interested to see if these steps solve this problem for you with a Debian etch kernel. Nate -- Nathaniel W. Turner http://aardvarque.com/
Attachment:
linux-2.6-misc-fix-vdso-in-core-dumps.patch
Description: Binary data
Attachment:
fix-vdso-in-core-dumps-rediff.patch
Description: Binary data