Closed p5pRT closed 21 years ago
This is a bug report for perl from DL-pdsupport@ubsw.com\, generated with the help of perlbug 1.34 running under perl v5.8.0.
Hi\,
I am getting a SIGSEGV\, Segmentation fault\, from miniperl during the build of perl 5.8.0 when I have these build options:
sh Configure \ -Dprefix='/tmp/perl/5.8.0-mt-debug' \ -Dprivlib='/tmp/perl/5.8.0-mt-debug/lib' \ -Darchlib='/tmp/perl/5.8.0-mt-debug/lib' \ -Dsitelib='/tmp/perl/5.8.0-mt-debug/lib' \ -Dsitearch='/tmp/perl/5.8.0-mt-debug/lib' \ -Dlocincpth='/sbcimp/run/pd/gdbm/1.8.0/include' \ -Dloclibpth='/sbcimp/run/pd/gdbm/1.8.0/lib' \ -Dcc=gcc \ -Dusethreads \ -Uinstallusrbinperl \ -Dperladmin='dl-pdsupport@ubsw.com' \ -Dcf_email='dl-pdsupport@ubsw.com' \ -Dccflags='-DLEAKTEST' \ -Doptimize='-g' \ -des
The build is successful if 1> -Dccflags='-DLEAKTEST' is removed or 2> -Dusethreads is removed i.e. it's the combination of multi thread + DLEAKTEST which is giving grief.
I'm building on Solaris 2.6: SunOS 5.6 Generic_105181-30 sun4u sparc SUNW\,Ultra-Enterprise
I'm building with gcc 3.1: gcc -v Reading specs from /sbcimp/run/pd/gcc/3.1/lib/gcc-lib/sparc-sun-solaris2.6/3.1/specs Configured with: /sbcimp/build/pd/gcc/gcc-3.1/configure --prefix=/sbcimp/run/pd/gcc/3.1 --enable-languages=c++ --enable-threads=solaris Thread model: solaris gcc version 3.1
The build error comes here: cp op.c opmini.c `sh cflags "optimize='-g'" opmini.o` -DPERL_EXTERNAL_GLOB opmini.c CCCMD = gcc -DPERL_CORE -c -D_REENTRANT -DLEAKTEST -DDEBUGGING -fno-strict-aliasing -I/sbcimp/run/pd/gdbm/1.8.0/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -Wall rm -f opmini.c gcc -L/sbcimp/run/pd/gdbm/1.8.0/lib -o miniperl \ miniperlmain.o opmini.o libperl.a -lsocket -lnsl -ldl -lm -lposix4 -lpthread -lc ./miniperl -w -Ilib -MExporter -e '\<?>' || make minitest Segmentation Fault - core dumped
Running the miniperl thru gdb shows:
ln4d419cmp> gdb ./miniperl GNU gdb 5.2.1 Copyright 2002 Free Software Foundation\, Inc. GDB is free software\, covered by the GNU General Public License\, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "sparc-sun-solaris2.6"... (gdb) run Starting program: /tmp/perl-5.8.0-mt-debug/miniperl [New LWP 1] [New LWP 2] [New LWP 3]
Program received signal SIGSEGV\, Segmentation fault. 0x000abaa0 in Perl_safexmalloc (x=31337\, size=344) at util.c:221 221 xycount[x][SIZE_TO_Y(size)]++; (gdb) bt #0 0x000abaa0 in Perl_safexmalloc (x=31337\, size=344) at util.c:221 #1 0x000c0b30 in Perl_reentrant_init (my_perl=0x210180) at reentr.c:143 #2 0x00046200 in perl_construct (my_perl=0x211ceb) at perl.c:275 #3 0x00025c0c in main (argc=1\, argv=0xeffffcb4\, env=0xeffffcbc) at miniperlmain.c:79
I'm not sure if this is a bug. Maybe -D_REENTRANT -DLEAKTEST aren't meant to work together ? Anyway\, I'm reporting it in case there's an easy fix.
Regards Judith dl-pdsupport@ubsw.com
Flags: category=install severity=low
Site configuration information for perl v5.8.0:
Configured by judithp at Thu Sep 12 12:52:10 BST 2002.
Summary of my perl5 (revision 5.0 version 8 subversion 0) configuration: Platform: osname=solaris\, osvers=2.6\, archname=sun4-solaris-thread-multi uname='sunos ln4d419cmp 5.6 generic_105181-30 sun4u sparc sunw\,ultra-enterprise ' config_args='-Dprefix=/tmp/perl/5.8.0-mt-debug -Dprivlib=/tmp/perl/5.8.0-mt-debug/lib -Darchlib=/tmp/perl/5.8.0-mt-debug/lib -Dsitelib=/tmp/perl/5.8.0-mt-debug/lib -Dsitearch=/tmp/perl/5.8.0-mt-debug/lib -Dlocincpth=/sbcimp/run/pd/gdbm/1.8.0/include -Dloclibpth=/sbcimp/run/pd/gdbm/1.8.0/lib -Dcc=gcc -Dusethreads -Uinstallusrbinperl -Dperladmin=dl-pdsupport@ubsw.com -Dcf_email=dl-pdsupport@ubsw.com -Doptimize=-g -des' hint=recommended\, useposix=true\, d_sigaction=define usethreads=define use5005threads=undef useithreads=define usemultiplicity=define useperlio=define d_sfio=undef uselargefiles=define usesocks=undef use64bitint=undef use64bitall=undef uselongdouble=undef usemymalloc=n\, bincompat5005=undef Compiler: cc='gcc'\, ccflags ='-D_REENTRANT -DDEBUGGING -fno-strict-aliasing -I/sbcimp/run/pd/gdbm/1.8.0/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64'\, optimize='-g'\, cppflags='-D_REENTRANT -DDEBUGGING -fno-strict-aliasing -I/sbcimp/run/pd/gdbm/1.8.0/include' ccversion=''\, gccversion='3.1'\, gccosandvers='solaris2.6' intsize=4\, longsize=4\, ptrsize=4\, doublesize=8\, byteorder=4321 d_longlong=define\, longlongsize=8\, d_longdbl=define\, longdblsize=16 ivtype='long'\, ivsize=4\, nvtype='double'\, nvsize=8\, Off_t='off_t'\, lseeksize=8 alignbytes=8\, prototype=define Linker and Libraries: ld='gcc'\, ldflags =' -L/sbcimp/run/pd/gdbm/1.8.0/lib ' libpth=/sbcimp/run/pd/gdbm/1.8.0/lib /usr/lib /usr/ccs/lib libs=-lsocket -lnsl -lgdbm -ldl -lm -lposix4 -lpthread -lc perllibs=-lsocket -lnsl -ldl -lm -lposix4 -lpthread -lc libc=/lib/libc.so\, so=so\, useshrplib=false\, libperl=libperl.a gnulibc_version='' Dynamic Linking: dlsrc=dl_dlopen.xs\, dlext=so\, d_dlsymun=undef\, ccdlflags=' ' cccdlflags='-fPIC'\, lddlflags='-G -L/sbcimp/run/pd/gdbm/1.8.0/lib'
Locally applied patches:
@INC for perl v5.8.0: /tmp/perl/5.8.0-mt-debug/lib /tmp/perl/5.8.0-mt-debug/lib /tmp/perl/5.8.0-mt-debug/lib /tmp/perl/5.8.0-mt-debug/lib .
Environment for perl v5.8.0: HOME=/sbclocal/sca LANG (unset) LANGUAGE (unset) LD_LIBRARY_PATH=/sbcimp/run/pd/gdbm/1.8.0/lib LOGDIR (unset) PATH=/tmp/perl/5.8.0-mt-debug/bin:/sbcimp/run/pd/gcc/3.1/bin:/sbin:/usr/sbin:/bin:/usr/ccs/bin:/usr/openwin/bin:/usr/dt/bin:/sbcimp/run/pd/gnutar/1.12/bin:/sbcimp/run/pd/gzip/1.2.4/bin PERL_BADLANG (unset) SHELL=/usr/bin/ksh
Visit our website at http://www.ubswarburg.com
This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate\, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system.
E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted\, corrupted\, lost\, destroyed\, arrive late or incomplete\, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments.
I am out of the office attending a coarse from the 9th September through 13th September.
For urgent issues please contact the SCA team on 85024 or raise a GRS request.
Visit our website at http://www.ubswarburg.com
This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate\, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system.
E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted\, corrupted\, lost\, destroyed\, arrive late or incomplete\, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments.
On 12 Sep 2002\, Dl-Pdsupport@Ubsw.Com wrote:
I am getting a SIGSEGV\, Segmentation fault\, from miniperl during the build of perl 5.8.0 when I have these build options:
i.e. it's the combination of multi thread + DLEAKTEST which is giving grief.
I'm not sure if this is a bug. Maybe -D_REENTRANT -DLEAKTEST aren't meant to work together ? Anyway\, I'm reporting it in case there's an easy fix.
Last I checked\, LEAKTEST didn't really work in any case\, and has not really been suppoted since before version 5.000. (Occasionally someone fixes things up to make it work\, but usually it gets broken again shortly thereafter.) Instead\, we recommend various third-party leak testers\, such as Purify or third degree.
-- Andy Dougherty doughera@lafayette.edu
On Fri 13 Sep 2002 01:51\, Andy Dougherty \doughera@​lafayette\.edu wrote:
On 12 Sep 2002\, Dl-Pdsupport@Ubsw.Com wrote:
I am getting a SIGSEGV\, Segmentation fault\, from miniperl during the build of perl 5.8.0 when I have these build options:
i.e. it's the combination of multi thread + DLEAKTEST which is giving grief.
I'm not sure if this is a bug. Maybe -D_REENTRANT -DLEAKTEST aren't meant to work together ? Anyway\, I'm reporting it in case there's an easy fix.
Last I checked\, LEAKTEST didn't really work in any case\, and has not really been suppoted since before version 5.000. (Occasionally someone fixes things up to make it work\, but usually it gets broken again shortly thereafter.) Instead\, we recommend various third-party leak testers\, such as Purify or third degree.
Remove it (with a rusty chainsaw)? Unsupport it from Configure? Undocument it?
If we don't use it ourselves\, and we have no value for it\, and valuable - free - third party tools (valgrind) are available\, why still keep it in?
-- H.Merijn Brand Amsterdam Perl Mongers (http://amsterdam.pm.org/) using perl-5.6.1\, 5.8.0 & 633 on HP-UX 10.20 & 11.00\, AIX 4.2\, AIX 4.3\, WinNT 4\, Win2K pro & WinCE 2.11. Smoking perl CORE: smokers@perl.org http://archives.develooper.com/daily-build@perl.org/ perl-qa@perl.org send smoke reports to: smokers-reports@perl.org\, QA: http://qa.perl.org
On Fri\, 13 Sep 2002\, H.Merijn Brand wrote:
On Fri 13 Sep 2002 01:51\, Andy Dougherty \doughera@​lafayette\.edu wrote:
Last I checked\, LEAKTEST didn't really work in any case\, and has not really been suppoted since before version 5.000. (Occasionally someone fixes things up to make it work\, but usually it gets broken again shortly thereafter.) Instead\, we recommend various third-party leak testers\, such as Purify or third degree.
Remove it (with a rusty chainsaw)? Unsupport it from Configure? Undocument it?
It is not "supported" in Configure -- it's not even mentioned. It's not "supported" in INSTALL -- it's not even mentioned. Odd\, though\, that someone added it to perlrun\, even though the below comment in handy.h is unchanged from 6 years ago:
XXX LEAKTEST doesn't really work in perl5. There are direct calls to safemalloc() in the source\, so LEAKTEST won't pick them up. (The main "offenders" are extensions.) Further\, if you try LEAKTEST\, you'll also end up calling Safefree\, which might call safexfree() on some things that weren't malloced with safexmalloc. The correct "fix" to this\, if anyone is interested\, is to ensure that all calls go through the New and Renew macros. --Andy Dougherty August 1996
It just never seemed worth the effort to go in and rip it out. It could potentially be made useful\, I suppose\, but for now I think LEAKTEST should be removed from perlrun.pod.
Andy Dougherty doughera@lafayette.edu
On Fri\, Sep 13\, 2002 at 08:51:17AM -0400\, Andy Dougherty wrote:
XXX LEAKTEST doesn't really work in perl5. There are direct calls to safemalloc() in the source\, so LEAKTEST won't pick them up. (The main "offenders" are extensions.) Further\, if you try LEAKTEST\, you'll also end up calling Safefree\, which might call safexfree() on some things that weren't malloced with safexmalloc. The correct "fix" to this\, if anyone is interested\, is to ensure that all calls go through the New and Renew macros. --Andy Dougherty August 1996
It just never seemed worth the effort to go in and rip it out. It could potentially be made useful\, I suppose\, but for now I think LEAKTEST should be removed from perlrun.pod.
It's also implied by the discussion of the -DL switch in perldebguts.pod; I got misled by that last week into trying to make -DLEAKTEST work\, before realizing it was too much of a blind alley.
-- Colin Watson [cjwatson@flatline.org.uk]
On Fri\, 13 Sep 2002\, Colin Watson wrote:
On Fri\, Sep 13\, 2002 at 08:51:17AM -0400\, Andy Dougherty wrote:
XXX LEAKTEST doesn't really work in perl5. There are direct calls to safemalloc() in the source\, so LEAKTEST won't pick them up. (The main "offenders" are extensions.)
It just never seemed worth the effort to go in and rip it out. It could potentially be made useful\, I suppose\, but for now I think LEAKTEST should be removed from perlrun.pod.
It's also implied by the discussion of the -DL switch in perldebguts.pod; I got misled by that last week into trying to make -DLEAKTEST work\, before realizing it was too much of a blind alley.
Well\, it clearly did work for someone (Ilya?) at least in some situations for a while. (It may all also have been very dependent upon whether or not perl's malloc or the system malloc was being used\, and whether or not EMBED_MY_MALLOC was or was not in force.) I suspect it's even more confused with threads. (At one point\, the threads extension actually called plain raw 'malloc()' directly\, bypassing both the New() interface and the safemalloc() interface. I haven't checked lately to see what's up.)
This sort of thing has always been the state with LEAKTEST. It almost works\, so it seems a shame to rip it out\, but it doesn't quite work.
-- Andy Dougherty doughera@lafayette.edu Dept. of Physics Lafayette College\, Easton PA 18042
Dl-Pdsupport@Ubsw.Com \perl5\-porters@​perl\.org writes:
# New Ticket Created by DL-pdsupport@ubsw.com # Please include the string: [perl #17197] # in the subject line of all future correspondence about this issue. # \<URL: http://rt.perl.org/rt2/Ticket/Display.html?id=17197 >
This is a bug report for perl from DL-pdsupport@ubsw.com\, generated with the help of perlbug 1.34 running under perl v5.8.0.
Hi\,
I am getting a SIGSEGV\, Segmentation fault\, from miniperl during the build of perl 5.8.0 when I have these build options:
The build is successful if 1> -Dccflags='-DLEAKTEST' is removed or 2> -Dusethreads is removed i.e. it's the combination of multi thread + DLEAKTEST which is giving grief.
Program received signal SIGSEGV\, Segmentation fault. 0x000abaa0 in Perl_safexmalloc (x=31337\, size=344) at util.c:221 221 xycount[x][SIZE_TO_Y(size)]++; (gdb) bt #0 0x000abaa0 in Perl_safexmalloc (x=31337\, size=344) at util.c:221 #1 0x000c0b30 in Perl_reentrant_init (my_perl=0x210180) at reentr.c:143 #2 0x00046200 in perl_construct (my_perl=0x211ceb) at perl.c:275 #3 0x00025c0c in main (argc=1\, argv=0xeffffcb4\, env=0xeffffcbc) at miniperlmain.c:79
I'm not sure if this is a bug. Maybe -D_REENTRANT -DLEAKTEST aren't meant to work together ? Anyway\, I'm reporting it in case there's an easy fix.
I don't think anyone has been maintaining the -DLEAKTEST stuff for a year or three. These days we tend to diagnose leaks with valgrind/purify rather than LEAKTEST's clever #fdefine hackery:
handy.h: XXX LEAKTEST doesn't really work in perl5. There are direct calls to handy.h: safemalloc() in the source\, so LEAKTEST won't pick them up.
-- Nick Ing-Simmons http://www.ni-s.u-net.com/
H.Merijn Brand \h\.m\.brand@​hccnet\.nl writes:
Remove it (with a rusty chainsaw)? Unsupport it from Configure? Undocument it?
If we don't use it ourselves\, and we have no value for it\, and valuable - free - third party tools (valgrind) are available\, why still keep it in?
I vote for removing it. One less #define forest to fight through.
-- Nick Ing-Simmons http://www.ni-s.u-net.com/
Andy Dougherty \doughera@​lafayette\.edu writes:
I suspect it's even more confused with threads. (At one point\, the threads extension actually called plain raw 'malloc()' directly\, bypassing both the New() interface and the safemalloc() interface. I haven't checked lately to see what's up.)
The direct use of malloc() was to bypass Win32's per-thread-pool scheme to try and allocate data global to all threads. I _think_ that should have been backed out now in favour of threads::shared and "proper" sv_dup() "cloning".
This sort of thing has always been the state with LEAKTEST. It almost works\, so it seems a shame to rip it out\, but it doesn't quite work. -- Nick Ing-Simmons http://www.ni-s.u-net.com/
Nick Ing-Simmons \nick@​ing\-simmons\.net writes:
H.Merijn Brand \h\.m\.brand@​hccnet\.nl writes:
Remove it (with a rusty chainsaw)? Unsupport it from Configure? Undocument it?
If we don't use it ourselves\, and we have no value for it\, and valuable - free - third party tools (valgrind) are available\, why still keep it in?
I vote for removing it. One less #define forest to fight through.
What about the systems without purify (I assume it's commercial) and valgrind (only for Linux/i386)?
Regards\, Slaven
-- Slaven Rezic - slaven.rezic@berlin.de babybike - routeplanner for cyclists in Berlin handheld (e.g. Compaq iPAQ with Linux) version of bbbike http://bbbike.sourceforge.net
Slaven Rezic \slaven\.rezic@​berlin\.de writes:
Nick Ing-Simmons \nick@​ing\-simmons\.net writes:
H.Merijn Brand \h\.m\.brand@​hccnet\.nl writes:
Remove it (with a rusty chainsaw)? Unsupport it from Configure? Undocument it?
If we don't use it ourselves\, and we have no value for it\, and valuable - free - third party tools (valgrind) are available\, why still keep it in?
I vote for removing it. One less #define forest to fight through.
What about the systems without purify (I assume it's commercial) and valgrind (only for Linux/i386)?
Well broadly speaking memory leaks are platform independant\, so we can find them on one that does. Personally I think a debugging malloc (tweaked version of perl's malloc ?) would be at least as good as LEAKTEST.
However if you want to side with Andy and leave it in that is okay too.
-- Nick Ing-Simmons http://www.ni-s.u-net.com/
On Sun\, Sep 15\, 2002 at 09:35:42PM +0200\, Slaven Rezic wrote:
[removing -DLEAKTEST]
What about the systems without purify (I assume it's commercial) and valgrind (only for Linux/i386)?
If you use google you can detect some message to a list about a FreeBSD guy working on a port sometime back in February\, but sadly nothing further seems to have happened.
I see no reason why valgrind could not be extended to any other CPU architecture if someone were brave enough to implement the code to translate its instructions to and from valgrind's internal representation.
Nicholas Clark -- Even better than the real thing: http://nms-cgi.sourceforge.net/
On Sun 15 Sep 2002 21:35\, Slaven Rezic \slaven\.rezic@​berlin\.de wrote:
Nick Ing-Simmons \nick@​ing\-simmons\.net writes:
H.Merijn Brand \h\.m\.brand@​hccnet\.nl writes:
Remove it (with a rusty chainsaw)? Unsupport it from Configure? Undocument it?
If we don't use it ourselves\, and we have no value for it\, and valuable - free - third party tools (valgrind) are available\, why still keep it in?
I vote for removing it. One less #define forest to fight through.
What about the systems without purify (I assume it's commercial) and valgrind (only for Linux/i386)?
The chances that LEAKTEST will be changed to *work* on those systems is problably about the same to the chance that valgrind is ported to such system
A *very* cheap solution might be to just link with the debugging version of GNU malloc\, but IIRC\, that ain't maintained anymore either.
Bottom line is that the code in there now is useless\, and there's no signals that it is to be made useful in the (near) future.
-- H.Merijn Brand Amsterdam Perl Mongers (http://amsterdam.pm.org/) using perl-5.6.1\, 5.8.0 & 633 on HP-UX 10.20 & 11.00\, AIX 4.2\, AIX 4.3\, WinNT 4\, Win2K pro & WinCE 2.11. Smoking perl CORE: smokers@perl.org http://archives.develooper.com/daily-build@perl.org/ perl-qa@perl.org send smoke reports to: smokers-reports@perl.org\, QA: http://qa.perl.org
On Sun\, 15 Sep 2002\, Nick Ing-Simmons wrote:
However if you want to side with Andy and leave it in that is okay too.
Me? I'm not taking any sides :-)\, just reporting history.
-- Andy Dougherty doughera@lafayette.edu
On Sun 15 Sep 2002 12:14\, Nick Ing-Simmons \nick@​ing\-simmons\.net wrote:
H.Merijn Brand \h\.m\.brand@​hccnet\.nl writes:
Remove it (with a rusty chainsaw)? Unsupport it from Configure? Undocument it?
If we don't use it ourselves\, and we have no value for it\, and valuable - free - third party tools (valgrind) are available\, why still keep it in?
I vote for removing it. One less #define forest to fight through.
Wrrrmmmmm\, wrmmmmmm\, crrrrrrrrrrrrrrrrrrrrrr LEAKTEST? What LEAKTEST?
Some small remarks.
a. I don't know if I caught the 'L' flag for -DDEBUGGING enough b. I don't know if I included generated files in the patch c. Tests still pass on HP-UX 11.00
Also attached for easier withdraw
H.Merijn Brand Amsterdam Perl Mongers (http://amsterdam.pm.org/) using perl-5.6.1\, 5.8.0 & 633 on HP-UX 10.20 & 11.00\, AIX 4.2\, AIX 4.3\, WinNT 4\, Win2K pro & WinCE 2.11. Smoking perl CORE: smokers@perl.org http://archives.develooper.com/daily-build@perl.org/ perl-qa@perl.org send smoke reports to: smokers-reports@perl.org\, QA: http://qa.perl.org
"H.Merijn Brand" \h\.m\.brand@​hccnet\.nl wrote:
a. I don't know if I caught the 'L' flag for -DDEBUGGING enough
There's a few DEBUG_L* symbols in perl.h that you can wipe out. Update also DEBUG_MASK in this same file.
The code that understands the letters after -D is in perl.c\, around line 2363 :
static char debopts[] = "psltocPmfrxuLHXDSTRJvC";
On Mon 16 Sep 2002 16:48\, Rafael Garcia-Suarez \raphel\.garcia\-suarez@​hexaflux\.com wrote:
"H.Merijn Brand" \h\.m\.brand@​hccnet\.nl wrote:
a. I don't know if I caught the 'L' flag for -DDEBUGGING enough
There's a few DEBUG_L* symbols in perl.h that you can wipe out. Update also DEBUG_MASK in this same file.
The code that understands the letters after -D is in perl.c\, around line 2363 :
static char debopts\[\] = "psltocPmfrxuLHXDSTRJvC";
OK\, grrr\, krack
H.Merijn Brand Amsterdam Perl Mongers (http://amsterdam.pm.org/) using perl-5.6.1\, 5.8.0 & 633 on HP-UX 10.20 & 11.00\, AIX 4.2\, AIX 4.3\, WinNT 4\, Win2K pro & WinCE 2.11. Smoking perl CORE: smokers@perl.org http://archives.develooper.com/daily-build@perl.org/ perl-qa@perl.org send smoke reports to: smokers-reports@perl.org\, QA: http://qa.perl.org
"H.Merijn Brand" \h\.m\.brand@​hccnet\.nl wrote:
OK\, grrr\, krack --- perl-current/perl.c 2002-09-04 16:07:19.000000000 +0200 +++ perl-current/perl.c 2002-09-16 16:57:59.000000000 +0200 @@ -2360\,7 +2360\,7 @@ Perl_moreswitches(pTHX_ char *s) forbid_setid("-D"); if (isALPHA(s[1])) { /* if adding extra options\, remember to update DEBUG_MASK */ - static char debopts[] = "psltocPmfrxuLHXDSTRJvC"; + static char debopts[] = "psltocPmfrxuHXDSTRJvC";
You're fast\, perhaps too fast. This should be static char debopts[] = "psltocPmfrxu HXDSTRJvC";
Hi\,
I am not in the office today. If your email is for sca or pd work or information\, please either raise a GRS request (GRSWeb -> Software Distribution Services -> SCA) or ask on the #sca-help chat channel.
Thanks Judith
Visit our website at http://www.ubswarburg.com
This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate\, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system.
E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted\, corrupted\, lost\, destroyed\, arrive late or incomplete\, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments.
Rafael Garcia-Suarez \raphel\.garcia\-suarez@​hexaflux\.com wrote:
"H.Merijn Brand" \h\.m\.brand@​hccnet\.nl wrote:
OK\, grrr\, krack --- perl-current/perl.c 2002-09-04 16:07:19.000000000 +0200 +++ perl-current/perl.c 2002-09-16 16:57:59.000000000 +0200 @@ -2360\,7 +2360\,7 @@ Perl_moreswitches(pTHX_ char *s) forbid_setid("-D"); if (isALPHA(s[1])) { /* if adding extra options\, remember to update DEBUG_MASK */ - static char debopts[] = "psltocPmfrxuLHXDSTRJvC"; + static char debopts[] = "psltocPmfrxuHXDSTRJvC";
You're fast\, perhaps too fast. This should be static char debopts[] = "psltocPmfrxu HXDSTRJvC";
Your patches (with my correction) build fine and passes all tests here.
And\, by the way\, there should be tests that -D\
On Mon 16 Sep 2002 18:03\, Rafael Garcia-Suarez \raphel\.garcia\-suarez@​hexaflux\.com wrote:
Rafael Garcia-Suarez \raphel\.garcia\-suarez@​hexaflux\.com wrote:
"H.Merijn Brand" \h\.m\.brand@​hccnet\.nl wrote:
OK\, grrr\, krack --- perl-current/perl.c 2002-09-04 16:07:19.000000000 +0200 +++ perl-current/perl.c 2002-09-16 16:57:59.000000000 +0200 @@ -2360\,7 +2360\,7 @@ Perl_moreswitches(pTHX_ char *s) forbid_setid("-D"); if (isALPHA(s[1])) { /* if adding extra options\, remember to update DEBUG_MASK */ - static char debopts[] = "psltocPmfrxuLHXDSTRJvC"; + static char debopts[] = "psltocPmfrxuHXDSTRJvC";
You're fast\, perhaps too fast. This should be static char debopts[] = "psltocPmfrxu HXDSTRJvC";
Your patches (with my correction) build fine and passes all tests here.
Feel free to apply. I won't so short before I leave for YAPC :)
And\, by the way\, there should be tests that -D\
and -D\<appropriate combination of letters> do the right thing. I'm just thinking aloud.
-- H.Merijn Brand Amsterdam Perl Mongers (http://amsterdam.pm.org/) using perl-5.6.1\, 5.8.0 & 633 on HP-UX 10.20 & 11.00\, AIX 4.2\, AIX 4.3\, WinNT 4\, Win2K pro & WinCE 2.11. Smoking perl CORE: smokers@perl.org http://archives.develooper.com/daily-build@perl.org/ perl-qa@perl.org send smoke reports to: smokers-reports@perl.org\, QA: http://qa.perl.org
"H.Merijn Brand" \h\.m\.brand@​hccnet\.nl wrote:
Feel free to apply. I won't so short before I leave for YAPC :)
Have a good time\, all. I'll stay in Lyon -- my day-job configuration makes impossible for me to take some vacation now. :(
On Mon\, Sep 16\, 2002 at 05:03:49PM +0200\, H.Merijn Brand wrote:
On Mon 16 Sep 2002 16:48\, Rafael Garcia-Suarez \raphel\.garcia\-suarez@​hexaflux\.com wrote:
"H.Merijn Brand" \h\.m\.brand@​hccnet\.nl wrote:
a. I don't know if I caught the 'L' flag for -DDEBUGGING enough
There's a few DEBUG_L* symbols in perl.h that you can wipe out. Update also DEBUG_MASK in this same file.
The code that understands the letters after -D is in perl.c\, around line 2363 :
static char debopts\[\] = "psltocPmfrxuLHXDSTRJvC";
OK\, grrr\, krack
--- perl-current/perl.c 2002-09-04 16:07:19.000000000 +0200 +++ perl-current/perl.c 2002-09-16 16:57:59.000000000 +0200 @@ -2360\,7 +2360\,7 @@ Perl_moreswitches(pTHX_ char *s) forbid_setid("-D"); if (isALPHA(s[1])) { /* if adding extra options\, remember to update DEBUG_MASK */ - static char debopts[] = "psltocPmfrxuLHXDSTRJvC"; + static char debopts[] = "psltocPmfrxuHXDSTRJvC"; char *d;
for \(s\+\+; \*s && \(d = strchr\(debopts\,\*s\)\); s\+\+\)
Are you going to add a warning on -L that says that leaktest is gone? Or just let the warning that they'll get:
Unrecognized switch: -L (-h will show valid options).
be enough of a hint to RTFM. I suspect that no-one not on p5p attempts to use leaktest\, so it's probably not worth a warning.
Nicholas Clark -- Even better than the real thing: http://nms-cgi.sourceforge.net/
"H.Merijn Brand" \h\.m\.brand@​hccnet\.nl wrote: :On Sun 15 Sep 2002 12:14\, Nick Ing-Simmons \nick@​ing\-simmons\.net wrote: :> I vote for removing it. One less #define forest to fight through. : :Wrrrmmmmm\, wrmmmmmm\, crrrrrrrrrrrrrrrrrrrrrr :LEAKTEST? What LEAKTEST?
Thanks. I think it makes sense to rip LEAKTEST out; your point that:
:The chances that LEAKTEST will be changed to *work* on those systems is :problably about the same to the chance that valgrind is ported to such system
seems the most relevant (except that I think the chance is much less - porting a valgrind-like tool would have much more general usefulness).
Could you submit a combined patch that includes the -DL removal and the correct debopts string? I'm vacillating on Nicholas' suggestion of a warning on -DL\, so I'll leave that one up to you.
Cheers\,
Hugo
On Mon 23 Sep 2002 18:14\, \hv@​crypt\.org wrote:
"H.Merijn Brand" \h\.m\.brand@​hccnet\.nl wrote: :On Sun 15 Sep 2002 12:14\, Nick Ing-Simmons \nick@​ing\-simmons\.net wrote: :> I vote for removing it. One less #define forest to fight through. : :Wrrrmmmmm\, wrmmmmmm\, crrrrrrrrrrrrrrrrrrrrrr :LEAKTEST? What LEAKTEST?
Thanks. I think it makes sense to rip LEAKTEST out; your point that:
:The chances that LEAKTEST will be changed to *work* on those systems is :problably about the same to the chance that valgrind is ported to such system
seems the most relevant (except that I think the chance is much less - porting a valgrind-like tool would have much more general usefulness).
Could you submit a combined patch that includes the -DL removal and
attached as combined
the correct debopts string? I'm vacillating on Nicholas' suggestion of a warning on -DL\, so I'll leave that one up to you.
No actions from this side now on this. Should we then also catch space?
a5:/u/usr/merijn 105 > perl -DH -le 'print$^O'
EXECUTING...
hpux a5:/u/usr/merijn 106 > perl -DL -le 'print$^O'
EXECUTING...
hpux a5:/u/usr/merijn 107 > perl -D\ -le 'print$^O'
EXECUTING...
hpux a5:/u/usr/merijn 108 > perl -Dq -le 'print$^O' Unrecognized switch: -q (-h will show valid options). a5:/u/usr/merijn 109 > perl -D\\367 -le 'print$^O' Unrecognized switch: -? (-h will show valid options). a5:/u/usr/merijn 110 >
Cheers\,
Hugo
-- H.Merijn Brand Amsterdam Perl Mongers (http://amsterdam.pm.org/) using perl-5.6.1\, 5.8.0 & 633 on HP-UX 10.20 & 11.00\, AIX 4.2\, AIX 4.3\, WinNT 4\, Win2K pro & WinCE 2.11. Smoking perl CORE: smokers@perl.org http://archives.develooper.com/daily-build@perl.org/ perl-qa@perl.org send smoke reports to: smokers-reports@perl.org\, QA: http://qa.perl.org
"H.Merijn Brand" \h\.m\.brand@​hccnet\.nl wrote: :> Could you submit a combined patch that includes the -DL removal and : :attached as combined
Thanks\, applied as #17920. No more LEAKTEST.
Hugo
Since the whole LEAKTEST feature seems to have grown obsolete\, and is now removed\, I'm marking the problem ticket as resolved.
@jhi - Status changed from 'new' to 'resolved'
Hi\,
I am not in the office today. If your email is for sca or pd work or information\, please either raise a GRS request (GRSWeb -> Software Distribution Services -> SCA) or ask on the #SDS_SCA chat channel.
Thanks Judith
Visit our website at http://www.ubswarburg.com
This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate\, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system.
E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted\, corrupted\, lost\, destroyed\, arrive late or incomplete\, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments.
@jhi - Status changed from 'open' to 'resolved'
Migrated from rt.perl.org#17197 (status was 'resolved')
Searchable as RT17197$