On 4/28/02 7:12 AM, "Puneet Kishor" <[EMAIL PROTECTED]> claimed:
> If I run the script from the command line I get the same, cryptic "Bus
> error" on the terminal. A little bit of research reveals that the error
> is probably because Perl tried to clear a memory pointer that doesn't
> exist any more. When I delve into the module I am using for my scripts,
> that indeed seems to be the case... the croaking seems to happen when
> the module tries to destroy an existing hash... specifically at...
>
> sub DESTROY {
> my $self = tied(%{$_[0]});
> delete $ITERATORS{$self};
> if (exists $OWNER{$self}) {
> mapscriptc::delete_mapObj($self);
> delete $OWNER{$self};
> }
> }
>
> In any case, here are my questions --
>
> 1. am I right about my assumption about failure to clear a memory
> pointer?
I don't know.
> 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 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.
David
--
David Wheeler AIM: dwTheory
[EMAIL PROTECTED] ICQ: 15726394
http://david.wheeler.net/ Yahoo!: dew7e
Jabber: [EMAIL PROTECTED]
