[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Possible mass bug filing: embedding perl hangs on hppa without PERL_SYS_INIT3


On Sun, Aug 10, 2008 at 10:59:38PM +0300, Niko Tyni wrote:
> as seen in #486069, since Perl 5.10.0, embedding Perl hangs on hppa
> in pthread_mutex_lock() inside perl_parse() if PERL_SYS_INIT3() hasn't
> been called.
> The need for PERL_SYS_INIT3() has been documented in perlembed.pod since
> Perl 5.8.1, so this is not a bug in perl.
> Quoting Carlos O'Donell in #486069:
> > The locked state of a lock is 0 on hppa, which means that if you don't
> > initialize your locks (as documented), they begin in the locked state
> > e.g. bss initialized to zero.
> >
> > You must use PERL_SYS_INIT3() on hppa, I don't know how it worked
> > without it.
> There are currently (at least) 26 source packages in unstable that
> produce binary packages linking against libperl5.10 on amd64 and whose
> .orig.tar.gz or .diff.gz matches /perl_parse/ but not /PERL_SYS_INIT3/.

This sounds like a valid reason for mass bug filing to me.

> The packages have different ways of accessing the embedded perl
> interpreter, and finding a way to verify the bug in each of them is pretty
> time consuming. Particularly so because I don't have an hppa machine of
> my own, and running for instance abiword over a slow network connection
> is probably going to take quite a while.
> Is there enough evidence here to file the bugs without actually testing
> for the lockup? If not, could somebody (from debian-hppa?) please take
> the lead in testing them?

Carlos O'Donell's explanation sounds like there should hardly be any
false positives, so this should imho be fine.


Sebastian "tokkee" Harl +++ GnuPG-ID: 0x8501C7FC +++ http://tokkee.org/

Those who would give up Essential Liberty to purchase a little Temporary
Safety, deserve neither Liberty nor Safety.         -- Benjamin Franklin

Attachment: signature.asc
Description: Digital signature

Reply to: