On Tue, Dec 18, 2007 at 12:36:00AM +0100, Michael Biebl wrote:
Hi, I need help with an RC against kdesvn. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=454179 In short: If the user runs the (amd64) version from the archive (0.14.1-1), it crashes with a SIBGUS error.
On amd64, the only two reasons for a SIGBUS are (a) as a result of mmap, or (b) as a result of bad hardware. Assuming (a) for now, mmap(2) says:
SIGBUS Attempted access to a portion of the buffer that does not cor‐ respond to the file (for example, beyond the end of the file, including the case where another process has truncated the file).Note that on other architectures, SIGBUS can also mean an unaligned access.
I asked the user to recompile kdesvn with the nostrip option, to get a backtrace, but this version doesn't crash for him. Even if he simply recompiles it without the nostrip option, it works for him.
It looks like, according to the strace, the KDE plugin loader is loading libkdesvnpart.so (*hopefully* through libdl/ld.so), and that once it's loaded the stack/data portions, something accesses the "gap" and the kernel raises a SIGBUS. It's really hard to tell what's going on here, but it could be a corrupt binary, a bug in the code that just happens to access that location, a bug in ld.so, or something else entirely.
What shall/can I do about this bug? Should I simply request a binNMU for amd64?
If that fixes the bug, then I don't see why you shouldn't. -- brian m. carlson / brian with sandals: Houston, Texas, US +1 713 440 7475 | http://crustytoothpaste.ath.cx/~bmc | My opinion only a typesetting engine: http://crustytoothpaste.ath.cx/~bmc/code/thwack OpenPGP: RSA v4 4096b 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187
Description: Digital signature