map command more than once causes crash

[GoogleCodeExporter]

Using aprq2 on linux, loading a map with 'map mapname' will load a map as
expected. If 'map mapname' is issued again, the client crashes.

This happens *every single time*, when instead the map should be loaded as
a new game.

This is the information given after the crash:
aq2: source/cc_utils.cpp:314: bool AssertExpression(bool, const char*):
Assertion `0' failed.

Original issue reported on code.google.com by toolma...@gmail.com on 2 Jun 2010 at 10:57

[GoogleCodeExporter]

I'm unable to reproduce this issue with Q2PRO and CCQ2 r432. Please test this 
with a 
non-CCQ2 game library to see if it still happens or not.

Original comment by Jayschwa on 3 Jun 2010 at 1:05

• Added labels: Engine-AprQ2

[GoogleCodeExporter]

I downloaded and built AprQ2 from jdolan's repository (his fork is newer). I 
was 
unable to reproduce the issue. My guess is that you're running an older version 
of 
AprQ2. I'm going to close the bug.

If you try jdolan's newer version and still have problems with just the CCQ2 
game 
library, go ahead and re-open it. It may indicate a problem with how the lib is 
being 
built on your machine.

Original comment by Jayschwa on 3 Jun 2010 at 2:03

• Changed state: Invalid

[GoogleCodeExporter]

I am using jdolan's aprq2, and this does not happen with other game binaries.
Building via the makefile in the SVN.

I am on an up-to-date Arch Linux machine.

Original comment by toolma...@gmail.com on 3 Jun 2010 at 4:30

[GoogleCodeExporter]

Can you try it with another engine like Q2PRO? It's pretty straight-forward to 
build.

svn://skuller.net/q2pro/trunk
./configure --enable-baseq2 --single-user && make

Original comment by Jayschwa on 3 Jun 2010 at 4:38

• Changed state: Accepted
• Added labels: OpSys-Linux

[GoogleCodeExporter]

Can you make us a stack trace? If we knew what function was crashing maybe we 
could
figure it out.

Original comment by Jonno.5000 on 3 Jun 2010 at 11:52

[GoogleCodeExporter]

Actually, "Assertion Failed" means that it hit AssertExpression.

Update to the latest revision I just committed, it should now print the assert
descriptive text BEFORE assert(0) (my fault for overlooking this). This should 
give
you the descriptive text in the Q2 console before it asserts, giving you a 
chance to
condump it or log it somehow.

Original comment by Jonno.5000 on 3 Jun 2010 at 4:27

[GoogleCodeExporter]

Fixed as of revision 435.

Original comment by toolma...@gmail.com on 3 Jun 2010 at 11:42

• Changed state: Verified

[GoogleCodeExporter]

Good to hear.

Original comment by Jayschwa on 4 Jun 2010 at 2:21

• Changed state: Fixed