Edward Moy wrote: > On Sunday, April 28, 2002, at 07:12 AM, Puneet Kishor wrote: > >> I am developing a web application, and have started encountering a >> new error (taken from the error_log)... >> >> [Sun Apr 28 08:50:40 2002] [error] (22)Invalid argument: getsockname >> [Sun Apr 28 08:50:40 2002] [notice] child pid 493 exit signal Bus >> error (10) >> [Sun Apr 28 08:50:40 2002] [notice] child pid 482 exit signal Bus >> error (10) >> >> >> [..] >> >> In any case, here are my questions -- >> >> 1. am I right about my assumption about failure to clear a memory >> pointer? >> 2. that the above error is new to me means that this is a problem >> specific to the module I am using, and not some new gremlin I have >> exposed in my iBook or the "Perl on MacOS X" implementation? > > > I've seen the bus error problem a lot myself, and after trying to > workaround the problem, occurring even in standard packages, I > concluded that it is a real bug in Perl 5.6.0, the default version > that comes with Mac OS X. Upgrading to 5.6.1 solved the bus error > problems for me.
sorry, I am running Perl 5.6.1. David Wheeler wrote: > >I think that it may be Mac OS X related, because I've run into it, too, but >couldn't nail it down. What I did find was that if I ran the script that >triggered the bus error in MallocDebug, the bus error never occurred! > >But if you can write a short test script that demonstrates the error >happening every time, it'd be worth sending in via perlbug. If you post it >here, we can also test it on our OS X and other systems, too. > > I'll see if I can do that, hoewver, this is happening in conjunction with a lot of related things, and there is a lot of data that gets munged by the scripts. Anyway, it is good to know that this is not a one-off problem. I have also alerted the writers of the perl module I am using that is causing this error to occur. Thanks everyone, pk/
