On Fri 03 Feb 2006, Steve Langasek wrote: > 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. :/)
No, "process already gone" or something like that. > > 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) Well, on alpha you get a kernel message with the address of the offending instruction, with a suitably compiled executable (-g) and gdb you can list the source line number where it occurs. > I remember seeing some comments about Sparc SIGBUS issues recently on the > upstream mailing list; so with luck this is already fixed upstream. Ah, that would be good. I'm getting a bit frustrated with the SIGBUSes on sparc, 'aptitude install non-existent-package' also suffers from it. And mysql, if it tries to resolve a hostname :-( thanks, Paul Slootman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
