http://bugzilla.spamassassin.org/show_bug.cgi?id=4376
------- Additional Comments From [EMAIL PROTECTED] 2005-06-03 07:49 ------- > Who'se problem this is > isn't real important yet, the important thing is to locate the difference > that seems to be resulting in perl doing a null pointer dereference. Once > the situation is understood a fix can be developed. agreed > Is there a way to run perl in some internal debug mode where it will spit > out a lot of information on what it is doing? It probably isn't running > very long before it crashes, so the debug result shouldn't be absolutely > huge. "perl -d", i suppose ... but i've ever used it to date, so not sure > Setting up to attach gdb to watch the crash would also be very > informative; but only if you know a lot about the insides of Perl itself. re perl debugging -- i'm in over my head here ... an occassional script is 1 thig, perl itself is another happy to help, i'll need some newbie style guidance -- here or offlie, doesn't matter > BTW, it might be worth checking on a Perl site or list and see if there is > any known similar problem with the OS that is causing you grief. This might > be a known (although possibly not solved) Perl bug. osx 10.4.1 bigs are a-plenty -- nothing specific, as yet tho ... ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
