From @khwilliamson

This is a bug report for perl from khw@​khw.(none),
generated with the help of perlbug 1.40 running under perl 5.22.0.

This is to make this email thread into a bug report so that it can be
tracked. See http​://nntp.perl.org/group/perl.perl5.porters/227690
and follow-up.

This is being made a blocker for 5.22 until we decide how to proceed.
One idea is to just not do locale handling on gcc for AIX for 5.22.
But this may be a machine configuration error. This isn't consistent
with things just breaking recently, unless there were other changes to
the now-failing machine at the time. A bisect would help figure that
out.

I have been granted access to that machine, but there isn't enough disk
space in my home directory to make a copy of the perl file structure and
compile and test.

Flags​:
  category=core
  severity=high

Site configuration information for perl 5.22.0​:

Configured by khw at Fri May 8 20​:27​:28 MDT 2015.

Summary of my perl5 (revision 5 version 22 subversion 0) configuration​:
  Commit id​: 2a2c1c1
  Platform​:
  osname=linux, osvers=3.16.0-37-generic,
archname=x86_64-linux-thread-multi-ld
  uname='linux khw 3.16.0-37-generic #51-ubuntu smp tue may 5
13​:45​:59 utc 2015 x86_64 x86_64 x86_64 gnulinux '
  config_args='-des -Uversiononly -Dprefix=/home/khw/blead -Dusedevel
-D'optimize=-ggdb3' -A'optimize=-ggdb3' -A'optimize=-O0'
-Accflags='-DPERL_BOOL_AS_CHAR' -Dman1dir=none -Dman3dir=none
-DDEBUGGING -Dcc=g++ -Dusemorebits -Dusethreads'
  hint=recommended, useposix=true, d_sigaction=define
  useithreads=define, usemultiplicity=define
  use64bitint=define, use64bitall=define, uselongdouble=define
  usemymalloc=n, bincompat5005=undef
  Compiler​:
  cc='g++', ccflags ='-D_REENTRANT -D_GNU_SOURCE -DPERL_BOOL_AS_CHAR
-fwrapv -DDEBUGGING -fno-strict-aliasing -pipe -fstack-protector-strong
-I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-D_FORTIFY_SOURCE=2',
  optimize=' -ggdb3 -O0',
  cppflags='-D_REENTRANT -D_GNU_SOURCE -DPERL_BOOL_AS_CHAR -fwrapv
-DDEBUGGING -fno-strict-aliasing -pipe -fstack-protector-strong
-I/usr/local/include'
  ccversion='', gccversion='4.9.1', gccosandvers=''
  intsize=4, longsize=8, ptrsize=8, doublesize=8, byteorder=12345678,
doublekind=3
  d_longlong=define, longlongsize=8, d_longdbl=define,
longdblsize=16, longdblkind=3
  ivtype='long', ivsize=8, nvtype='long double', nvsize=16,
Off_t='off_t', lseeksize=8
  alignbytes=16, prototype=define
  Linker and Libraries​:
  ld='g++', ldflags =' -fstack-protector-strong -L/usr/local/lib'
  libpth=/usr/include/c++/4.9 /usr/include/x86_64-linux-gnu/c++/4.9
/usr/include/c++/4.9/backward /usr/local/lib
/usr/lib/gcc/x86_64-linux-gnu/4.9/include-fixed
/usr/include/x86_64-linux-gnu /usr/lib /lib/x86_64-linux-gnu /lib/../lib
/usr/lib/x86_64-linux-gnu /usr/lib/../lib /lib
  libs=-lpthread -lnsl -ldl -lm -lcrypt -lutil -lc
  perllibs=-lpthread -lnsl -ldl -lm -lcrypt -lutil -lc
  libc=libc-2.19.so, so=so, useshrplib=false, libperl=libperl.a
  gnulibc_version='2.19'
  Dynamic Linking​:
  dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags='-Wl,-E'
  cccdlflags='-fPIC', lddlflags='-shared -ggdb3 -ggdb3 -O0
-L/usr/local/lib -fstack-protector-strong'

Locally applied patches​:
  RC0

@​INC for perl 5.22.0​:
  /home/khw/perl/blead/lib
  /home/khw/blead/lib/perl5/site_perl/5.22.0/x86_64-linux-thread-multi-ld
  /home/khw/blead/lib/perl5/site_perl/5.22.0
  /home/khw/blead/lib/perl5/5.22.0/x86_64-linux-thread-multi-ld
  /home/khw/blead/lib/perl5/5.22.0
  /home/khw/blead/lib/perl5/site_perl/5.21.12
  /home/khw/blead/lib/perl5/site_perl/5.21.11
  /home/khw/blead/lib/perl5/site_perl/5.21.10
  /home/khw/blead/lib/perl5/site_perl/5.21.9
  /home/khw/blead/lib/perl5/site_perl/5.21.8
  /home/khw/blead/lib/perl5/site_perl/5.21.7
  /home/khw/blead/lib/perl5/site_perl/5.21.6
  /home/khw/blead/lib/perl5/site_perl/5.21.5
  /home/khw/blead/lib/perl5/site_perl/5.21.4
  /home/khw/blead/lib/perl5/site_perl/5.21.3
  /home/khw/blead/lib/perl5/site_perl/5.21.2
  /home/khw/blead/lib/perl5/site_perl/5.21.1
  /home/khw/blead/lib/perl5/site_perl/5.20.0
  /home/khw/blead/lib/perl5/site_perl/5.19.12
  /home/khw/blead/lib/perl5/site_perl/5.19.11
  /home/khw/blead/lib/perl5/site_perl/5.19.10
  /home/khw/blead/lib/perl5/site_perl
  .

Environment for perl 5.22.0​:
  HOME=/home/khw
  LANG=en_US.UTF-8
  LANGUAGE=en_US
  LD_LIBRARY_PATH (unset)
  LOGDIR (unset)

PATH=/home/khw/bin​:/home/khw/perl5/perlbrew/bin​:/home/khw/print/bin​:/bin​:/usr/local/sbin​:/usr/local/bin​:/usr/sbin​:/usr/bin​:/sbin​:/usr/games​:/usr/local/games​:/home/khw/iands/www​:/home/khw/cxoffice/bin
  PERL5OPT=-w
  PERL_BADLANG (unset)
  PERL_POD_PEDANTIC=1
  SHELL=/bin/ksh

From @khwilliamson

I don't think this is a Perl problem, and I know it isn't a new Perl problem, so I have removed it as a 5.22 blocker.

Michael granted me access to a failing machine, and I downloaded and compiled 5.20.2 and got the same failure. This proves it isn't a regression introduced in the 5.21 series, so it isn't a 5.22 blocker.

I don't know why it suddenly showed up. Michael speculated to me privately that the xlc smoke reports were masking the gcc ones, as this shows up only with gcc.

And, given that truss and dbx are indicating a failing libc call, it seems pretty unlikely to be a Perl bug.

--
Karl Williamson

The RT System itself - Status changed from 'new' to 'open'

From @iabyn

On Sun, May 10, 2015 at 10​:11​:16AM -0700, Karl Williamson via RT wrote​:

I don't think this is a Perl problem, and I know it isn't a new Perl problem, so I have removed it as a 5.22 blocker.

Michael granted me access to a failing machine, and I downloaded and compiled 5.20.2 and got the same failure. This proves it isn't a regression introduced in the 5.21 series, so it isn't a 5.22 blocker.

I don't know why it suddenly showed up. Michael speculated to me privately that the xlc smoke reports were masking the gcc ones, as this shows up only with gcc.

And, given that truss and dbx are indicating a failing libc call, it seems pretty unlikely to be a Perl bug.

Hi Karl, any particular reason why this ticket has been marked as a 5.26.0
blocker?

--
I don't want to achieve immortality through my work...
I want to achieve it through not dying.
  -- Woody Allen

From @khwilliamson

On 03/20/2017 09​:34 AM, Dave Mitchell wrote​:

On Sun, May 10, 2015 at 10​:11​:16AM -0700, Karl Williamson via RT wrote​:

I don't think this is a Perl problem, and I know it isn't a new Perl problem, so I have removed it as a 5.22 blocker.

Michael granted me access to a failing machine, and I downloaded and compiled 5.20.2 and got the same failure. This proves it isn't a regression introduced in the 5.21 series, so it isn't a 5.22 blocker.

I don't know why it suddenly showed up. Michael speculated to me privately that the xlc smoke reports were masking the gcc ones, as this shows up only with gcc.

And, given that truss and dbx are indicating a failing libc call, it seems pretty unlikely to be a Perl bug.

Hi Karl, any particular reason why this ticket has been marked as a 5.26.0
blocker?

See http​://nntp.perl.org/group/perl.perl5.porters/243217

All BBC tickets should be reviewed to decide if they should be blockers.

From @iabyn

On Mon, Mar 20, 2017 at 10​:40​:11AM -0600, Karl Williamson wrote​:

On 03/20/2017 09​:34 AM, Dave Mitchell wrote​:

On Sun, May 10, 2015 at 10​:11​:16AM -0700, Karl Williamson via RT wrote​:

I don't think this is a Perl problem, and I know it isn't a new Perl problem, so I have removed it as a 5.22 blocker.

Michael granted me access to a failing machine, and I downloaded and compiled 5.20.2 and got the same failure. This proves it isn't a regression introduced in the 5.21 series, so it isn't a 5.22 blocker.

I don't know why it suddenly showed up. Michael speculated to me privately that the xlc smoke reports were masking the gcc ones, as this shows up only with gcc.

And, given that truss and dbx are indicating a failing libc call, it seems pretty unlikely to be a Perl bug.

Hi Karl, any particular reason why this ticket has been marked as a 5.26.0
blocker?

See http​://nntp.perl.org/group/perl.perl5.porters/243217

All BBC tickets should be reviewed to decide if they should be blockers.

In that case, do you think it should be a blocker, either for 5.26.0 or
any other release? My feeling is not, but this isn't my area of expertise.

--
Art is anything that has a label (especially if the label is "untitled 1")

From @khwilliamson

On 03/20/2017 11​:04 AM, Dave Mitchell wrote​:

On Mon, Mar 20, 2017 at 10​:40​:11AM -0600, Karl Williamson wrote​:

On 03/20/2017 09​:34 AM, Dave Mitchell wrote​:

On Sun, May 10, 2015 at 10​:11​:16AM -0700, Karl Williamson via RT wrote​:

I don't think this is a Perl problem, and I know it isn't a new Perl problem, so I have removed it as a 5.22 blocker.

Michael granted me access to a failing machine, and I downloaded and compiled 5.20.2 and got the same failure. This proves it isn't a regression introduced in the 5.21 series, so it isn't a 5.22 blocker.

I don't know why it suddenly showed up. Michael speculated to me privately that the xlc smoke reports were masking the gcc ones, as this shows up only with gcc.

And, given that truss and dbx are indicating a failing libc call, it seems pretty unlikely to be a Perl bug.

Hi Karl, any particular reason why this ticket has been marked as a 5.26.0
blocker?

See http​://nntp.perl.org/group/perl.perl5.porters/243217

All BBC tickets should be reviewed to decide if they should be blockers.

In that case, do you think it should be a blocker, either for 5.26.0 or
any other release? My feeling is not, but this isn't my area of expertise.

I merely did a bulk move. I don't think this should be a blocker

From @khwilliamson

Michael, since this ticket was opened, new debugging has been added so that we can more easily see what's going on. If you could take a recent version of blead, compiled with -DDEBUGGING, and with this set​:

export PERL_DEBUG_LOCALE_INIT=1

and run your test again on it, and send us the output

--
Karl Williamson

From @khwilliamson

I have now removed this from the list of 5.26 blockers, and renamed it so that it won't get added again.

--
Karl Williamson

From @aixtools

I had many system changes, among them one of the systems I could
borrowed - and died. I'll look into setting up a single partition to
run blead again - versus the eight I had running before.

Hope that helps!

Michael

On Sat, Mar 25, 2017 at 2​:30 AM, Karl Williamson via RT
<perlbug-followup@​perl.org> wrote​:

Michael, since this ticket was opened, new debugging has been added so that we can more easily see what's going on. If you could take a recent version of blead, compiled with -DDEBUGGING, and with this set​:

export PERL_DEBUG_LOCALE_INIT=1

and run your test again on it, and send us the output

--
Karl Williamson

---
via perlbug​: queue​: perl5 status​: open
https://rt-archive.perl.org/perl5/Ticket/Display.html?id=125142

From @khwilliamson

On Tue, 28 Mar 2017 08​:02​:26 -0700, aixtools@​gmail.com wrote​:

I had many system changes, among them one of the systems I could
borrowed - and died. I'll look into setting up a single partition to
run blead again - versus the eight I had running before.

Hope that helps!

Michael

On Sat, Mar 25, 2017 at 2​:30 AM, Karl Williamson via RT
<perlbug-followup@​perl.org> wrote​:

Michael, since this ticket was opened, new debugging has been added
so that we can more easily see what's going on. If you could take a
recent version of blead, compiled with -DDEBUGGING, and with this
set​:

export PERL_DEBUG_LOCALE_INIT=1

and run your test again on it, and send us the output

--
Karl Williamson

---
via perlbug​: queue​: perl5 status​: open
https://rt-archive.perl.org/perl5/Ticket/Display.html?id=125142

Any status on this?
--
Karl Williamson

From @khwilliamson

No response from OP in a year; marking this stalled
--
Karl Williamson

@khwilliamson - Status changed from 'open' to 'stalled'

No respone in 4 years; closing