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 <[EMAIL PROTECTED]> wrote: > > > On Sun, 13 Feb 2005 10:03:30 -0500 > > Brian Fundakowski Feldman <[EMAIL PROTECTED]> 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... -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> [EMAIL PROTECTED] \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\ _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"
