Crashes at end of race with abort call from STL

Bug #1695950 reported by LaunchpadLoginDefectReport
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Extreme Tux Racer
New
Undecided
Unassigned

Bug Description

Crashes at end of race, because of an range error detected by the STL. See stack backtrace.

This is repeatable. To repeat:

1. Start program. Select Practice/Extras/Desperation
2. Do not follow track. Go straight ahead off cliff.
3. When trees reached, go right, around trees, near
    cliff.
4. Look ahead for two sets of trees with a gap between. Go through gap.
5. Hard right, then hard left.
6. There's a ramp. Go up the ramp at full speed, on right third of ramp.
7. This puts you on the flat top of the cliffs, above the track.
8. Go to right edge of world and follow until cliff drops.
9. Fall off cliff. Continue along right edge of world to rising cliff.
10. Climb vertical cliff by approaching it slowly along edge of world,
    then press up arrow. Tux will climb and slow. When climbing slows,
    press left arrow, and climbing will accelerate and take Tux over
    the top. This may take a few tries.
11. Continue along right edge of world until progress bar is almost full.
12. Turn left, slow down, and carefully go off cliff at left, falling onto
    track.
13. Proceed on track to finish line.
14. As Tux reaches finish line, program will abort.

This is repeatable. It will even occur under GDB. Haven't built with debug symbols to get a better backtrace, though.

Tags: abort crash stl
Revision history for this message
LaunchpadLoginDefectReport (nagle-1) wrote :
Revision history for this message
LaunchpadLoginDefectReport (nagle-1) wrote :

If you do steps 1-11 above, but don't turn left and just continue along the right edge of the world to the end, there is no crash. The crash only occurs if the end is reached while in the left half of the world.

Revision history for this message
LaunchpadLoginDefectReport (nagle-1) wrote :

Now crashing at the end of other tracks. This seems to depend on the contents of the high score list. Crashes seem to occur when the high score list is full and being changed.

Revision history for this message
LaunchpadLoginDefectReport (nagle-1) wrote :

Nothing to do with the track. It's a bug in the high score list update. Something is going wrong when a high score list has all 10 entries and a new one has to replace an old one.

Removing the high score list file stops crashing, at least until it fills up again.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.