Re: Bug#486069: Bug#494191: eperl: Hangs on hppa
(dropping #494191 from the Cc's)
On Fri, Aug 08, 2008 at 08:37:48AM -0400, Carlos O'Donell wrote:
> On Fri, Aug 8, 2008 at 4:04 AM, Niko Tyni <firstname.lastname@example.org> wrote:
> > On Thu, Aug 07, 2008 at 08:51:51PM +0200, Rafael Laboissiere wrote:
> >> Package: eperl
> >> Version: 2.2.14-15.1+b1
> >> Severity: serious
> >> Justification: renders package unusable on hppa
> >> eperl hangs on hppa, even for this trivial case:
> >> eperl /dev/null
> > See #486069: embedding perl hangs on hppa without PERL_SYS_INIT3() since 5.10.0
> > There's a list of probably broken packages there that I haven't had the
> > time to go through yet.
> > Cc'ing the debian-hppa and debian-perl lists again in the hope somebody
> > could pick this up and test them.
> I'm not clear on the action item here? What do you need tested?
Well, I'm not quite comfortable with filing grave (or even 'important')
bugs based on a quick grep without actually testing for the brokenness.
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.
> 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.
Thanks for the explanation, it's pretty much what I had figured out but
it's nice to have a porter statement.
I suppose a debian-devel announcement in the usual mass bug filing
procedure would be a good next step. If somebody else wants to lead this,
be my guest.
Note that inn and inn2 have since been fixed AFAIK, so there's something
like 26 more suspected packages left.
Niko Tyni email@example.com