[fofix-gcode-issuetracker] Issue 1278 in fofix: Floating Point Exception in FoFiX 3.121 and git

[fofix at googlecode.com]

Status: New
Owner: ----
Labels: Priority-Low

New issue 1278 by dbz11.2... at gmail.com: Floating Point Exception in FoFiX  
3.121 and git
http://code.google.com/p/fofix/issues/detail?id=1278

Describe the problem. What did you expect? What do you see?
FoFiX 3.121 and git crash during song initialization.

Fatal Python error: (pygame parachute) Floating Point Exception
Aborted

List the steps to recreate the problem.
1. Start FoFiX
2. Quickplay
3. Pick profile, instrument, etc
4. Before it finishes initializing, game crashes

What version are you using? Include the FoFiX version, the Python version,
your operating system, and whether it is Git, alpha, beta, RC, or final
release.  (If it's Git, please include the commit hash.)
FoFiX 3.121 final
FoFiX git e827e7b012516a56ae80ab03865d1d84b0a4db02
Python 2.6.8
Debian Wheezy, kernel 3.2.0-3-amd64, all packages up-to-date at the time of  
writing

Log file attached for 3.121 final (fofix.log) and git (fofix4.log).

Please provide any additional information below.

 From what I've been able to figure out, it's caused by (or at least happens  
with) pyvorbis 1.5, which is the latest version in the Wheezy repos.  
Installing 1.4 from Squeeze (package metadata modified to get it to  
install) works fine, which led me to think it's a problem in pyvorbis 1.5.

I commented on a bug report marked CantReproduce last night talking about  
this but hadn't realized that this one is actually a little different one  
than they were experiencing. I read their report wrong, as it apparently  
didn't click that their problem was a segfault where mine is a floating  
point exception, and that it happens later in the game than theirs. So,  
decided to post this instead. I didn't see any reports on it, so I  
apologize if there is one and I'm just blind.

Attachments:
	fofix.log  7.2 KB
	fofix4.log  22.1 KB