Comment 33 for bug 985100

Another bug was reported (bug #1191889 ), which was about a different topic, but the real underlying problem was the same as this bug.
I could track the problem down to a 0 pointer of the next transportation step. Maybe WareInstance::get_next_move_step is returning a 0 pointer under some circumstances, although it should not???