Decided to check the core dump that perl left behind but this is all i see(minus a couple thousand lines above this point with no more detail than given here:
#1345 0x102454ff in ?? () #1346 0x1424448d in ?? () #1347 0x5440f750 in ?? () #1348 0x00020000 in ?? () #1349 0x688e0375 in ?? () #1350 0x0158b814 in ?? () #1351 0xcd500000 in ?? () #1352 0x90feeb80 in ?? () #1353 0x282d9b04 in ?? () #1354 0x00000001 in ?? () #1355 0xbfbfeeb8 in ?? () #1356 0x00000004 in ?? () Cannot access memory at address 0xbfc00000 (gdb) Sean wrote: > On Thu, 10 Sep 2009, Eric Sheesley wrote: > > [mail.log snipped] > > > What's in /var/log/messages? Or dmesg? > > I started having amavisd-new cause perl to coredump, apparently deep in > the middle of > Converter::UULib when a coredump was forced. > > >>> Regards, >> _______________________________________________ >> freebsd-ports@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-ports >> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" >> _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"