http://bugzilla.spamassassin.org/show_bug.cgi?id=4376
------- Additional Comments From [EMAIL PROTECTED] 2005-06-03 00:18 ------- Subject: Re: SA (v303/snap) 'make' fails (Bus Error) @ "spamc" on OSX 10.4.1 + WORKAROUND > however on 10.4.1 -- actually, now on 2 separate boxes -- the BusError continues to occur. > > <confused> richard </confused> If Perl and the hardware is the same but the os is different, and this results in a crash, I can say (as an ex OS designer) that this means that one OS is giving some different response to Perl on some sort of query, and Perl isn't expecing the response it is getting. 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. 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. 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. 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. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
