Page 1 of 1

[Resolved 0.4.1] segfault when removing rails. [reproduced]

Posted: Sat May 04, 2013 8:58 am
by MF-
(I am trying to create "steps to reproduce right now...)

This has happened while pursuing a "dense multi-track station" idea, trying to fill the empty spots of
Image

Ultimately building this: (Regardless of actual utility of such build :P)
Image


FOOTER: Please don't think of this bug storm as a proof that you haven't tested it properly.
Take it as a proof that the distributed bughunting is really effective and the way to go.

Re: [0.4.0] segfault when removing rails... [reproduced]

Posted: Sat May 04, 2013 11:27 am
by MF-
So.. here goes a picture-by-picture howto.. (eh.. max 3 pictures...
I guess I am forced to do a GIF...) And to include it via Image

Two non-moving pictures of the later stages of the build
bug3.png
bug3.png (671.62 KiB) Viewed 4505 times
bug4.png
bug4.png (660.98 KiB) Viewed 4505 times

Re: [0.4.0] segfault when removing rails... [reproduced]

Posted: Sat May 04, 2013 12:04 pm
by MF-
PS: I even got a segfault while placing rails this time

Re: [0.4.0] segfault when removing rails... [reproduced]

Posted: Sat May 04, 2013 12:37 pm
by MF-
PPS: It also segfaults when I stand in the "trident-like" contraption from the first post, the "select new research" thing pops up by itself and I dismiss it by "t" instead of selecting new research.

Re: [0.4.0] segfault when removing rails... [reproduced]

Posted: Sat May 04, 2013 12:38 pm
by kovarex
Thank you for the nice setup, we just repaired the bug.

Re: [0.4.0] segfault when removing rails... [reproduced]

Posted: Sat May 04, 2013 12:51 pm
by kovarex
MF- wrote:PPS: It also segfaults when I stand in the "trident-like" contraption from the first post, the "select new research" thing pops up by itself and I dismiss it by "t" instead of selecting new research.
Thank you, fixed.

Re: [0.4.0] segfault when removing rails... [reproduced]

Posted: Sat May 04, 2013 1:43 pm
by slpwnd
MF- wrote: FOOTER: Please don't think of this bug storm as a proof that you haven't tested it properly.
Take it as a proof that the distributed bughunting is really effective and the way to go.
Actually we are really grateful for you guys being willing to download and test the game even when it is most probably going to cause problems. Some of the bugs we could have found but some of them would take a long time to find. So yes the "distributed bughunting" looks very appealing. As long as people understand that the version released after month of work will be rather unstable all is good.