Skip Menu |

This queue is for tickets about the Schedule-Cron CPAN distribution.

Report information
The Basics
Id: 50860
Status: rejected
Priority: 0/
Queue: Schedule-Cron
People
Owner: roland [...] cpan.org
Requestors: develop [...] traveljury.com
Cc:
AdminCc:
Bug Information
Severity: Important
Broken in: 0.99
Fixed in: (no value)

History Show all quoted text
  Tue Oct 27 04:25:33 2009 develop [...] traveljury.com - Ticket created
Subject: panic: attempt to copy value 1 to a freed scalar
Hi Roland I've been running version 0.99 for a couple of weeks, without incident. Then last night, I had this message twice, presumably from two processes: "panic: attempt to copy value 1 to a freed scalar a51828c at /opt/perl-5.8.9/lib/site_perl/5.8.9/Schedule/Cron.pm line 1042." Clint Summary of my perl5 (revision 5 version 8 subversion 9) configuration: Platform: osname=linux, osvers=2.6.21.7-2.fc8xen, archname=i686-linux uname='linux dev.iannounce.co.uk 2.6.21.7-2.fc8xen #1 smp fri feb 15 12:39:36 est 2008 i686 gnulinux ' config_args='-Dprefix=/opt/perl-5.8.9 -des -Di_db -Di_dbm -Di_ndbm -Di_gdbm -Duseshrplib=true -Doptimize=-O2 -fmessage-length=0 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -g -Wall -pipe -Accflags=-D_REENTRANT -D_GNU_SOURCE -DPERL_USE_SAFE_PUTENV -fno-strict-aliasing -pipe -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -Acppflags=-D_REENTRANT -D_GNU_SOURCE -DPERL_USE_SAFE_PUTENV -DDEBUGGING -fno-strict-aliasing -pipe -Dnoextensions=NDBM_File' hint=recommended, useposix=true, d_sigaction=define usethreads=undef use5005threads=undef useithreads=undef usemultiplicity=undef useperlio=define d_sfio=undef uselargefiles=define usesocks=undef use64bitint=undef use64bitall=undef uselongdouble=undef usemymalloc=n, bincompat5005=undef Compiler: cc='cc', ccflags ='-D_REENTRANT -D_GNU_SOURCE -DPERL_USE_SAFE_PUTENV -fno-strict-aliasing -pipe -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DDEBUGGING -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64', optimize='-O2 -fmessage-length=0 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -g -Wall -pipe', cppflags='-D_REENTRANT -D_GNU_SOURCE -DPERL_USE_SAFE_PUTENV -DDEBUGGING -fno-strict-aliasing -pipe -D_REENTRANT -D_GNU_SOURCE -DPERL_USE_SAFE_PUTENV -fno-strict-aliasing -pipe -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DDEBUGGING -I/usr/local/include' ccversion='', gccversion='4.2.4 (Ubuntu 4.2.4-1ubuntu4)', gccosandvers='' intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=1234 d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12 ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='off_t', lseeksize=8 alignbytes=4, prototype=define Linker and Libraries: ld='cc', ldflags =' -L/usr/local/lib' libpth=/usr/local/lib /lib /usr/lib /usr/lib64 libs=-lnsl -lgdbm -ldb -ldl -lm -lcrypt -lutil -lc perllibs=-lnsl -ldl -lm -lcrypt -lutil -lc libc=/lib/libc-2.7.so, so=so, useshrplib=true, libperl=libperl.so gnulibc_version='2.7' Dynamic Linking: dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags='-Wl,-E -Wl,-rpath,/opt/perl-5.8.9/lib/5.8.9/i686-linux/CORE' cccdlflags='-fPIC', lddlflags='-shared -O2 -fmessage-length=0 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -g -Wall -pipe -L/usr/local/lib' Characteristics of this binary (from libperl): Compile-time options: DEBUGGING PERL_MALLOC_WRAP PERL_USE_SAFE_PUTENV USE_FAST_STDIO USE_LARGE_FILES USE_PERLIO Built under linux Compiled at Oct 6 2009 19:32:33 @INC: /opt/perl-5.8.9/lib/5.8.9/i686-linux /opt/perl-5.8.9/lib/5.8.9 /opt/perl-5.8.9/lib/site_perl/5.8.9/i686-linux /opt/perl-5.8.9/lib/site_perl/5.8.9
  Wed Oct 28 09:52:43 2009 roland [...] cpan.org - Taken
  Wed Oct 28 10:13:52 2009 roland [...] cpan.org - Correspondence added
Hi Clint, On Tue Oct 27 04:25:33 2009, DRTECH wrote: Show quoted text
> I've been running version 0.99 for a couple of weeks, without incident. > Then last night, I had this message twice, presumably from two processes: > > "panic: attempt to copy value 1 to a freed scalar a51828c at > /opt/perl-5.8.9/lib/site_perl/5.8.9/Schedule/Cron.pm line 1042."
That's really strange and I'm afraid, I cant do much about this. This is an perl internal message for a failure happening during memory management. A pure perl module like Schedule::Cron doesn't do any explicite memory management on its own and relies completely on the the underlying perl interpreter. The good thing here is that it can't be made responsible formemory allocation faults at all (though for memory leaks, its a different story ;-) Also strange: In Schedule::Cron version 0.99 the line 1042 is an empty line. Can you please verify that /opt/perl-5.8.9/lib/site_perl/5.8.9/Schedule/Cron.pm indeed point to version 0.99 of Schedule::Cron ? (look for $VERSION near the top of the file) To conclude, I really think its a perl inernal problem, maybe due to the way how it is compiled. The same fault should occur for other modules as well.
  Wed Oct 28 10:13:52 2009 The RT System itself - Status changed from 'new' to 'open'
  Wed Oct 28 10:21:49 2009 develop [...] traveljury.com - Correspondence added
On Wed Oct 28 10:13:52 2009, ROLAND wrote: Show quoted text
> Hi Clint, >
Show quoted text
> > Also strange: In Schedule::Cron version 0.99 the line 1042 is an > empty line. Can you please verify that > /opt/perl-5.8.9/lib/site_perl/5.8.9/Schedule/Cron.pm indeed point > to version 0.99 of Schedule::Cron ? (look for $VERSION near the > top of the file)
Whoops! It was version 0.97. My apologies. The line in question was : $STARTEDCHILD{$pid} = 1; just after forking Never mind - I've installed 0.99 again, and will let you know if there are any futher issues. sorry :) clint
  Wed Oct 28 10:21:50 2009 develop [...] traveljury.com - Status changed from 'open' to 'rejected'