On 8/13/07, Joe Wells <[EMAIL PROTECTED]> wrote:
>
> Okay, I'm really stopping after this. :-) No more time for testing.
>
> • BUG:I got a segmentation violation when pressing right mouse
> button to switch the contents of the right panel. The game was
> paused at the time, so I can be pretty sure that the crash resulted
> from switching the panel. Of course, there is no core dump file, so
> I can't help figure out why.
I can't reproduce this bug/
• BUG:I am getting glibc/malloc corruption crashes.
>
> I got a crash with this message:
>
> *** glibc detected *** free(): invalid next size (normal): 0x08d38da0
> ***
>
> This seems to have happened while formatting a message for display
> on the screen. This is bug #20771.
>
> I also got a crash with this message:
>
> *** glibc detected *** double free or corruption (out): 0x08d95b98 ***
>
> This seems to have happened while deconstructing a Game object (when
> exiting the editor). This is bug #20772.
>
> I got yet another crash with this message:
>
> *** glibc detected *** corrupted double-linked list: 0x090845d0 ***
>
> This happened when I was overrunning the enemy base and seems to
> have been triggered by deconstructing a Building object. This is
> also part of bug #20772.
I will further investigate this.
• BUG: The game got into a state where most of the commands were being
> delayed by about 15 seconds. Things that were delayed: pausing (the
> "p" key), quitting (from the menu), adjusting number of requested
> globules or radius on a flag. Things that still worked instantly:
> moving the viewport with mouse or keyboard, dragging flags. The
> game was almost over so I didn't get much more experience with this.
Most likely due to excessive use of scroll wheel. Quitting, pausing are
queued through the game engine. Scroll wheel bug is fixed.
• BUG:The fertility map sometimes completely does not work (nothing
> shows anywhere). But sometimes (later in the same game) it works
> fine.
Not sure what causes this. The computation thread automatically spawns at 4
seconds in, and it takes another 4 seconds to complete.
• BUG (old, I think):The damage map is not working. It doesn't show
> anything, despite lots of damaged globules.
Fixed.
• When glob2 is run the very first time (and there is no ~/.glob2
> directory yet), it prints this error message:
>
> Settings::load("preferences.txt") : error, can't open file.
Fixed.
Given that this is a normal course of events, it would be better if
> no error message were printed to avoid scaring the user.
>
> • It would be better if the fertility map did not highlight areas with
> stone on them, given that nothing can ever grow where there is
> stone.
When I did this before, I noticed that it created very ugly holes in the
gradient, even though it was more accurrate, it was less asphetic.
I hope these comments are helpful.
>
> --
> Joe
>
>
> _______________________________________________
> glob2-devel mailing list
> [email protected]
> http://lists.nongnu.org/mailman/listinfo/glob2-devel
>
--
Extra cheese comes at a cost. Bradley Arsenault.
_______________________________________________
glob2-devel mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/glob2-devel
