Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Number-Phone CPAN distribution.

Report information
The Basics
Id: 65557
Status: resolved
Priority: 0/
Queue: Number-Phone

People
Owner: Nobody in particular
Requestors: MSTEVENS [...] cpan.org
Cc: michael.smith [...] dianomi.com
michael.stevens [...] dianomi.com
AdminCc:

Bug Information
Severity: Unimportant
Broken in: 1.8
Fixed in: (no value)



CC: michael.stevens [...] dianomi.com,michael.smith [...] dianomi.com
Subject: Use of uninitialized variable errors
Use of uninitialized value $subscriberlength in substitution (s///) at /opt/dianomi/perl/lib/site_perl/5.12.2/Number/Phone/UK.pm line 106. Use of uninitialized value $arealength in substr at /opt/dianomi/perl/lib/site_perl/5.12.2/Number/Phone/UK.pm line 107. Use of uninitialized value $arealength in substr at /opt/dianomi/perl/lib/site_perl/5.12.2/Number/Phone/UK.pm line 108. Use of uninitialized value $subscriberlength in numeric ne (!=) at /opt/dianomi/perl/lib/site_perl/5.12.2/Number/Phone/UK.pm line 114. Admittedly I don't have the input. Summary of my perl5 (revision 5 version 12 subversion 2) configuration: Platform: osname=linux, osvers=2.6.18-194.26.1.el5, archname=x86_64-linux uname='linux 303646-web1.dianomi.co.uk 2.6.18-194.26.1.el5 #1 smp fri oct 29 14:21:16 edt 2010 x86_64 x86_64 x86_64 gnulinux ' config_args='-des -Dprefix=/opt/dianomi/perl -Accflags=-fPIC' hint=recommended, useposix=true, d_sigaction=define useithreads=undef, usemultiplicity=undef useperlio=define, d_sfio=undef, uselargefiles=define, usesocks=undef use64bitint=define, use64bitall=define, uselongdouble=undef usemymalloc=n, bincompat5005=undef Compiler: cc='cc', ccflags ='-fPIC -fno-strict-aliasing -pipe -fstack- protector -I/usr/local/include -D_LARGEFILE_SOURCE - D_FILE_OFFSET_BITS=64', optimize='-O2', cppflags='-fPIC -fno-strict-aliasing -pipe -fstack-protector - I/usr/local/include' ccversion='', gccversion='4.1.2 20080704 (Red Hat 4.1.2-48)', gccosandvers='' intsize=4, longsize=8, ptrsize=8, doublesize=8, byteorder=12345678 d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=16 ivtype='long', ivsize=8, nvtype='double', nvsize=8, Off_t='off_t', lseeksize=8 alignbytes=8, prototype=define Linker and Libraries: ld='cc', ldflags =' -fstack-protector -L/usr/local/lib' libpth=/usr/local/lib /lib /usr/lib /lib64 /usr/lib64 /usr/local/lib64 libs=-lnsl -ldb -ldl -lm -lcrypt -lutil -lc perllibs=-lnsl -ldl -lm -lcrypt -lutil -lc libc=/lib/libc-2.5.so, so=so, useshrplib=false, libperl=libperl.a gnulibc_version='2.5' Dynamic Linking: dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags='-Wl,-E' cccdlflags='-fPIC', lddlflags='-shared -O2 -L/usr/local/lib -fstack- protector' Characteristics of this binary (from libperl): Compile-time options: PERL_DONT_CREATE_GVSV PERL_MALLOC_WRAP USE_64_BIT_ALL USE_64_BIT_INT USE_LARGE_FILES USE_PERLIO USE_PERL_ATOF Built under linux Compiled at Jan 11 2011 13:45:15 @INC: /opt/dianomi/perl/lib/site_perl/5.12.2/x86_64-linux /opt/dianomi/perl/lib/site_perl/5.12.2 /opt/dianomi/perl/lib/5.12.2/x86_64-linux /opt/dianomi/perl/lib/5.12.2 .
This is almost certainly down to OFCOM introducing some new data format in their CSV files that I've not spotted. I'll put in a work-around that *should* make it go away, but it would be Really Helpful if you could find what the data is that provokes this, so that I can write a test case. In the meantime I'm marking this as resolved so that it disappears from my to-do list. If you do find which number provoked it, please raise another ticket.
Subject: Re: [rt.cpan.org #65557] Use of uninitialized variable errors
Date: Wed, 20 Jul 2011 18:36:52 +0100
To: David Cantrell via RT <bug-Number-Phone [...] rt.cpan.org>
From: Michael Stevens <mstevens [...] etla.org>
On Tue, Jul 19, 2011 at 05:50:15PM -0400, David Cantrell via RT wrote: Show quoted text
> <URL: https://rt.cpan.org/Ticket/Display.html?id=65557 > > > This is almost certainly down to OFCOM introducing some new data format in their CSV files that > I've not spotted. I'll put in a work-around that *should* make it go away, but it would be Really > Helpful if you could find what the data is that provokes this, so that I can write a test case. > > In the meantime I'm marking this as resolved so that it disappears from my to-do list. If you do > find which number provoked it, please raise another ticket.
I think I've identified at least one number that triggers this, and raised another ticket as requested. Michael
thanks