From allen@huarp.harvard.edu

Numerous SIGSEGV's during make test, none of which were present
in 5.5.670. This report is preliminary, just to raise a flag, but
if anyone has any clues, let me know.

  op/defins
  pragma/constant
  pragma/locale
  pragma/strict (twice)
  lib/fatal
  lib/fields
  lib/gol-basic
  lib/gol-compat
  lib/gol-linkage
  lib/opcode
  lib/open2
  lib/open3
  lib/safe1
  lib/safe2

FWIW, I'm getting some "pointer type mismatch" warnings in
pp_sys.c and doio.c. Don't know if they were there before​:
will check. -Norton Allen

This perlbug was built using Perl v5.6.0 - Thu Mar 09 16:13:03 est 2000
It is being executed now by  Perl v5.5.670 - Wed Mar 01 09:37:32 est 2000.

Site configuration information for perl v5.5.670:

Configured by nort at Wed Mar 01 09:37:32 est 2000.

Summary of my perl5 (revision 5.0 version 5 subversion 670) configuration:
  Platform:
    osname=qnx, osvers=424, archname=x86-qnx
    uname='qnx 53 g 424 pci 32 '
    config_args='-des -Dman1dir=/usr/local/man/man1 -Dman3dir=/usr/local/man/man3'
    hint=recommended, useposix=true, d_sigaction=define
    usethreads=undef use5005threads=undef useithreads=undef usemultiplicity=undef
    useperlio=undef d_sfio=undef uselargefiles=define 
    use64bitint=undef use64bitall=undef uselongdouble=undef usesocks=undef
  Compiler:
    cc='cc', optimize='-O', gccversion=
    cppflags='-mf -w4 -Wc,-wcd=202 -Wc,-wcd=203 -Wc,-wcd=302 -Wc,-fi=unix.h -I/usr/local/include'
    ccflags ='-mf -w4 -Wc,-wcd=202 -Wc,-wcd=203 -Wc,-wcd=302 -Wc,-fi=unix.h -I/usr/local/include'
    stdchar='unsigned char', d_stdstdio=define, usevfork=false
    intsize=4, longsize=4, ptrsize=4, doublesize=8
    d_longlong=undef, longlongsize=, d_longdbl=define, longdblsize=8
    ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='off_t', lseeksize=4
    alignbytes=1, usemymalloc=y, prototype=define
  Linker and Libraries:
    ld='ld', ldflags ='-g -N1M -L/usr/local/lib'
    libpth=/usr/local/lib /usr/lib
    libs=-lsocket -lcrypt -lunix
    libc=/usr/lib/clib3r.lib, so=none, useshrplib=false, libperl=libperl3r.lib
  Dynamic Linking:
    dlsrc=dl_none.xs, dlext=none, d_dlsymun=undef, ccdlflags=''
    cccdlflags='', lddlflags=''

Locally applied patches:
    v5.6.0-RC1


@INC for perl v5.5.670:
    /usr/local/lib/perl5/5.5.670/x86-qnx
    /usr/local/lib/perl5/5.5.670
    /usr/local/lib/perl5/site_perl/5.5.670/x86-qnx
    /usr/local/lib/perl5/site_perl/5.5.670
    /usr/local/lib/perl5/site_perl
    .


Environment for perl v5.5.670:
    HOME=//2/home/nort
    LANG (unset)
    LANGUAGE (unset)
    LD_LIBRARY_PATH (unset)
    LOGDIR (unset)
    PATH=:/bin:/usr/bin:/usr/local/bin:/usr/ucb
    PERL_BADLANG (unset)
    SHELL=/bin/sh

From [Unknown Contact. See original ticket]

Norton Allen wrote​:

Numerous SIGSEGV's during make test, none of which were present
in 5.5.670. This report is preliminary, just to raise a flag, but
if anyone has any clues, let me know.

  The SIGSEGV's go away when compiled with debugging, so it
  appears to be something that breaks under optimization.
  Does anyone familiar with the changes between 5.670 and 5.6
  have any guesses as where to start looking for something that
  might be common to the following test failures?

op/defins
pragma/constant
pragma/locale
pragma/strict (twice)
lib/fatal
lib/fields
lib/gol-basic
lib/gol-compat
lib/gol-linkage
lib/opcode
lib/open2
lib/open3
lib/safe1
lib/safe2

FWIW, I'm getting some "pointer type mismatch" warnings in
pp_sys.c and doio.c. Don't know if they were there before​:
will check. -Norton Allen

  The same warnings were in fact present in 5.5.670 without
  SIGSEGVs.

  -Norton
 

From [Unknown Contact. See original ticket]

At 11​:16 -0500 2000-03-10, Norton Allen wrote​:

The SIGSEGV's go away when compiled with debugging, so it
appears to be something that breaks under optimization.

Not necessarily​: by default, there's extra slack in the malloc
overhead union in a debugging perl. I've seen this hide problems.
You can get rid of it by compiling malloc.c with -DNO_RCHECK. See
the comments at the start of the file.
--
Dominic Dunlop

From [Unknown Contact. See original ticket]

Dominic Dunlop wrote​:

At 11​:16 -0500 2000-03-10, Norton Allen wrote​:

The SIGSEGV's go away when compiled with debugging, so it
appears to be something that breaks under optimization.

Not necessarily​: by default, there's extra slack in the malloc
overhead union in a debugging perl. I've seen this hide problems.
You can get rid of it by compiling malloc.c with -DNO_RCHECK. See
the comments at the start of the file.

OK, that's next. All the SIGSEGVs are at the same address, and
it's in Perl_pad_allocmy_ (op.c). I'll try -g again with
-DNO_RCHECK and see if I can get some source. -Norton

From [Unknown Contact. See original ticket]

Dominic Dunlop wrote​:

At 11​:16 -0500 2000-03-10, Norton Allen wrote​:

The SIGSEGV's go away when compiled with debugging, so it
appears to be something that breaks under optimization.

Not necessarily​: by default, there's extra slack in the malloc
overhead union in a debugging perl. I've seen this hide problems.
You can get rid of it by compiling malloc.c with -DNO_RCHECK. See
the comments at the start of the file.

I built with -g and no DEBUGGING and the problem did not manifest
itself. I assume if DEBUGGING isn't present, then the NO_RCHECK
thing is moot? -Norton

From [Unknown Contact. See original ticket]

Norton Allen writes​:

I built with -g and no DEBUGGING and the problem did not manifest
itself. I assume if DEBUGGING isn't present, then the NO_RCHECK
thing is moot? -Norton

Correct.

Ilya