Am Freitag, 2. Januar 2009 01:31:07 schrieb Dennis Schridde:
> Author: devurandom
> Date: Fri Jan 2 01:31:05 2009
> New Revision: 6524
>
> URL: http://svn.gna.org/viewcvs/warzone?rev=6524&view=rev
> Log:
> fix bug #4831 (Endlessly spinning droids)
That should have been bug #12363... 4831 is the nu
#196: Script tries to build demolish for defense around oil derrick
---+
Reporter: Per| Owner: gerard
Type: defect | Status: new
Priority:
On Thu, Jan 1, 2009 at 6:30 PM, Dennis Schridde wrote:
> Am Donnerstag, 1. Januar 2009 18:22:40 schrieb Per Inge Mathisen:
>> On Thu, Jan 1, 2009 at 4:26 PM, Dennis Schridde wrote:
>> > Can you not just skip asserts in the debugger?
>>
>> Can you? Ever since the crash handler was added, I always
Am Donnerstag, 1. Januar 2009 18:22:40 schrieb Per Inge Mathisen:
> On Thu, Jan 1, 2009 at 4:26 PM, Dennis Schridde wrote:
> > Can you not just skip asserts in the debugger?
>
> Can you? Ever since the crash handler was added, I always end up in a
> non-skippable abort inside it when trying to ski
On Thu, Jan 1, 2009 at 4:26 PM, Dennis Schridde wrote:
> Can you not just skip asserts in the debugger?
Can you? Ever since the crash handler was added, I always end up in a
non-skippable abort inside it when trying to skip an assert in the
debugger.
> And there are still assert()s, which are di
Am Donnerstag, 1. Januar 2009 15:54:26 schrieb Per Inge Mathisen:
> On Thu, Jan 1, 2009 at 3:39 PM, Per Inge Mathisen
>
> wrote:
> > This patch adds a new cheat "noassert" which turns off asserts. ASSERT
> > calls will still generate log entries, but not take down the program.
> > This is meant fo
On Thu, Jan 1, 2009 at 3:39 PM, Per Inge Mathisen
wrote:
> This patch adds a new cheat "noassert" which turns off asserts. ASSERT
> calls will still generate log entries, but not take down the program.
> This is meant for testing that code hit by an assert bug has
> sufficient error handling that
This patch adds a new cheat "noassert" which turns off asserts. ASSERT
calls will still generate log entries, but not take down the program.
This is meant for testing that code hit by an assert bug has
sufficient error handling that it can survive when compiled without
assertions. Which it always s
