You're right, Hans.  Subsequent testing shows that I'm seeing wierdness in code 
which doesn't have anything to do with Moose.  

Here's another sample trace:

Maximal count of pending signals (120) exceeded at 
/home/nypntdev/iprs_perl/lib/5.12.2/x86_64-linux/DynaLoader.pm line 200.
Compilation failed in require at 
/home/nypntdev/iprs_perl/lib/site_perl/5.12.1/Cache/CacheUtils.pm line 19.
BEGIN failed--compilation aborted at 
/home/nypntdev/iprs_perl/lib/site_perl/5.12.1/Cache/CacheUtils.pm line 19.
Compilation failed in require at 
/home/nypntdev/iprs_perl/lib/site_perl/5.12.1/Cache/BaseCache.pm line 18.
BEGIN failed--compilation aborted at 
/home/nypntdev/iprs_perl/lib/site_perl/5.12.1/Cache/BaseCache.pm line 18.
Compilation failed in require at 
/home/nypntdev/iprs_perl/lib/site_perl/5.12.1/Cache/FileCache.pm line 17.
BEGIN failed--compilation aborted at 
/home/nypntdev/iprs_perl/lib/site_perl/5.12.1/Cache/FileCache.pm line 17.
Compilation failed in require at 
/home/nypntdev/lib/site_perl/DEV/POINT/Server.pm line 113.
BEGIN failed--compilation aborted at 
/home/nypntdev/lib/site_perl/DEV/POINT/Server.pm line 113.
Compilation failed in require at 
/home/nypntdev/lib/site_perl/DEV/POINT/POINTDBI.pm line 23.
BEGIN failed--compilation aborted at 
/home/nypntdev/lib/site_perl/DEV/POINT/POINTDBI.pm line 23.
Compilation failed in require at 
/home/erberg/lib/site_perl/DEV/POINT/SVN/Collection.pm line 18.
BEGIN failed--compilation aborted at 
/home/erberg/lib/site_perl/DEV/POINT/SVN/Collection.pm line 18.
Compilation failed in require at 
/home/erberg/work/batch-scripts/bin/svnvalidate line 22.
BEGIN failed--compilation aborted at 
/home/erberg/work/batch-scripts/bin/svnvalidate line 22.
Caught a SIGFPE at 
/home/nypntdev/iprs_perl/lib/site_perl/5.12.1/x86_64-linux/DBI.pm line 519
Modification of a read-only value attempted at 
/home/nypntdev/iprs_perl/lib/5.12.2/sigtrap.pm line 99.
END failed--call queue aborted at 
/home/erberg/work/batch-scripts/bin/svnvalidate line 22.
 
Something's quite wonky with this perl.  I built this a while ago and have had 
only success until this afternoon.  I'm trying to get my group migrated off of 
5.8.0.  This is kind of a bummer.

Any suggestions on where to take this problem?  I think I'm going to post on 
perlmonks.org, but suggestions on an approach to tracking this problem down 
would be appreciated.

Eric

> -----Original Message-----
> From: Hans Dieter Pearcey [mailto:h...@pobox.com] 
> Sent: Thursday, December 02, 2010 5:22 PM
> To: Berg, Eric: IT (NYK); n...@nickandperla.net; moose@perl.org
> Subject: RE: Floating Point Exception
> 
> On Thu, 2 Dec 2010 16:22:38 -0500, 
> <eric.b...@barclayscapital.com> wrote:
> > > > > > Caught a SIGFPE
> > > > > > at /home/nypntdev/iprs_perl/lib/perl5/x86_64-linux/
> > > > > > List/MoreUtils.pm line 29 $ = eval {...}
> 
> Shouldn't you be looking here?  I'm not sure this has 
> anything to do with Moose
> at all.
> 
> hdp.
> 
_______________________________________________

This e-mail may contain information that is confidential, privileged or 
otherwise protected from disclosure. If you are not an intended recipient of 
this e-mail, do not duplicate or redistribute it by any means. Please delete it 
and any attachments and notify the sender that you have received it in error. 
Unless specifically indicated, this e-mail is not an offer to buy or sell or a 
solicitation to buy or sell any securities, investment products or other 
financial product or service, an official confirmation of any transaction, or 
an official statement of Barclays. Any views or opinions presented are solely 
those of the author and do not necessarily represent those of Barclays. This 
e-mail is subject to terms available at the following link: 
www.barcap.com/emaildisclaimer. By messaging with Barclays you consent to the 
foregoing.  Barclays Capital is the investment banking division of Barclays 
Bank PLC, a company registered in England (number 1026167) with its registered 
office at 1 Churchill Place, London, E14 5HP.  This email may relate to or be 
sent from other members of the Barclays Group.
_______________________________________________

Reply via email to