[VPM] perl segfault

[abez]

Ok I sent the report in, quoted a bunch of emails etc.

abram

On Fri, 13 Feb 2004, Peter Scott wrote:

> [BTW, are we meeting this month, and when?  Darren?]
> 
> At 05:04 PM 2/13/2004 -0800, abez wrote:
> >My supervisor (Dr. German) stumbled across a perl segfault. I 
> >determined what it was.
> >
> >He was printf'ing a string that contained the substring  %ve
> >
> >If you type at the commandline
> >perl -e "printf '%ve'"; echo $?
> >
> >You will notice the program segfaults and returns with code 139
> >(interesting enough this is the netbios/samba port).
> >
> >I've determined it's the printf trying to print a double which doesn't
> >exist and isn't a double.
> >
> >It doesn't sound very serious but imagine you use a printf in a web app
> >and the user types in a %ve..
> >
> >So if you could test this in your versions it'd be nice.
> 
> 5.6.1 on Solaris:
> 
> % perl -e 'printf "%ve"; print "\n"'; echo $status
> 0.000000e+00
> 0
> 
> 5.8.1 on Fedora core:
> $ perl -e 'printf "%ve"; print "\n"'; echo $status
> Segmentation fault (core dumped)
> 139
> 
> 5.6.0 on Fedora core:
> $ ./perl -e 'printf "%ve"; print "\n"' ; echo $status0.000000e+00
> 0
> 
> perl 5.8.3 on Fedora core:
> $ ./perl -e 'printf "%ve"; print "\n"' ; echo $status
> Segmentation fault (core dumped)
> 139
> 
> Fairly recent bleadperl on Fedora core:
> $ ./perl -e 'printf "%ve"; print "\n"' ; echo $status
> Segmentation fault (core dumped)
> 139
> 
> 
> I think you've found a bug... go ahead and dust off perlbug and claim 
> the honour and glory...
> 
> 
> 

-- 
abez ------------------------------------------
http://www.abez.ca/ Abram Hindle (abez at abez.ca)
------------------------------------------ abez