Date: Sun, 13 Feb 2005 20:25:59 +0200 From: Ion-Mihai Tetcu <itetcu@people.tecnik93.com> To: Brian Fundakowski Feldman <green@freebsd.org> Cc: freebsd-hackers@freebsd.org Subject: Re: SIGBUS help, please Message-ID: <20050213202559.38e1f1af@it.buh.tecnik93.com> In-Reply-To: <20050213170437.GB63697@green.homeunix.org> References: <20050210225558.7a0879ec@it.buh.cameradicommercio.ro> <20050213150330.GI65523@green.homeunix.org> <20050213182616.036ba07a@it.buh.tecnik93.com> <20050213184752.611ce46c@it.buh.tecnik93.com> <20050213170437.GB63697@green.homeunix.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 13 Feb 2005 12:04:37 -0500 Brian Fundakowski Feldman <green@freebsd.org> wrote: > On Sun, Feb 13, 2005 at 06:47:52PM +0200, Ion-Mihai Tetcu wrote: > > On Sun, 13 Feb 2005 18:26:16 +0200 > > Ion-Mihai Tetcu <itetcu@people.tecnik93.com> wrote: > > > > > On Sun, 13 Feb 2005 10:03:30 -0500 > > > Brian Fundakowski Feldman <green@freebsd.org> wrote: > > > > > > > On Thu, Feb 10, 2005 at 10:55:58PM +0200, Ion-Mihai Tetcu wrote: > > > > > Hi, > > > > > > > > > > > > > > > One of my ports - mail/dspam-devel stays at 3.4 because newer versions > > > > > crash on FreeBSD (they work on Linux and Solaris). > > > > > Can someone make some sense from the output bellow ? > > > > > > > > > > I'm willing to make a port and help with all needed setup information - > > > > > a 5-10 minutes job if someone has the time for it. > > > > > > > > Have you tried valgrind in any of its modes yet? > > > > > > I wouldn't have posted here without reaching my level of incompetence > > > first :-/ > > > > > > Beginning with 3.3.2 dspam's author has rewritten a lot of code > > > involving threads and with his help I've managed to make it work on > > > FreeBSD and so I can run 3.3.4 in production. After 3.3.4 I haven't been > > > able to keep up with him and besides this crash, which mask it, there is > > > at least an other threading bug on FreeBSD. > > > > Not that I'm understanding why, but _right now_, run from gdb or not it > > works, even if I deliver multiple messages in parallel. And this > > inconsistent behaviour it's not a local problem, I've reproduced it on 2 > > boxes and got users reports too. I'm really loss :( > > > > In valgrind, on the other hand, --trace-pthread=all --trace-signals=yes it dies: > > Have you tried helgrind? That seems to be the one to try next. The default > stack trace size it keeps is not very large, so you may want to increase it > to 100 or so before you go to debugging these. These 4 errors probably are > genuine bugs and could be the root cause of the crash that's occurring... On this it works 5.3-STABLE FreeBSD 5.3-STABLE #0: Thu Feb 10 17:38:05 EET 2005 root@it.buh.tecnik93.com:/usr/obj/usr/src/sys/IT53_U i386 this kernel has ULE On this it crash 5.3-STABLE FreeBSD 5.3-STABLE #17: Mon Jan 17 23:40:22 EET 2005 itetcu@it.buh.cameradicommercio.ro:/usr/obj/usr/src/sys/IT53_d i386 this 4BSD WTF ?? -- IOnut Unregistered ;) FreeBSD "user"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050213202559.38e1f1af>