Hi Paul, On Fri, Feb 03, 2006 at 01:03:07PM +0100, Paul Slootman wrote:
> I did an upgrade yesterday, and since then I'm being bombarded with > "Segfault in Samba" email messages. Did those emails not include a usable backtrace? (Possibly not, since I'm told gdb doesn't handle -fPIE very well, which is now a default upstream. :/) > Note that the email subject is wrong: it's not a SIGSEGV, it's a SIGBUS. Yeah, known bug. :) > On sparc, unfortunately, I don't know how to track these down :-( > I'll try to reproduce it on an alpha (the kernel there is helpful enough > to report such accesses and to fix them up, although there's a > significant speed penalty). Eh, it's far easier to debug a sigbus on sparc than it is on alpha, since you have to go to so much effort just to get the signal to userspace on alpha... (which, completely randomly, I'm working on fixing by porting prctl to alpha, but that'll require a new kernel anyway) I remember seeing some comments about Sparc SIGBUS issues recently on the upstream mailing list; so with luck this is already fixed upstream. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/
signature.asc
Description: Digital signature
