Bug#351234: samba: SIGBUS on sparc since upgrading to 3.0.21a-1

2006-02-03 Thread Steve Langasek
On Fri, Feb 03, 2006 at 02:46:33PM +0100, Paul Slootman wrote: > 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

Bug#351234: samba: SIGBUS on sparc since upgrading to 3.0.21a-1

2006-02-03 Thread Paul Slootman
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

Bug#351234: samba: SIGBUS on sparc since upgrading to 3.0.21a-1

2006-02-03 Thread Steve Langasek
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,

Bug#351234: samba: SIGBUS on sparc since upgrading to 3.0.21a-1

2006-02-03 Thread Paul Slootman
Package: samba Version: 3.0.21a-1 Severity: normal I did an upgrade yesterday, and since then I'm being bombarded with "Segfault in Samba" email messages. >From smbd.log: [2006/02/03 12:25:51, 1] smbd/service.c:make_connection_snum(666) jop (192.168.170.196) connect to service data initially a