Source Code Project Mantis - FSSCP
View Issue Details
0001991FSSCP---------public2009-09-14 04:542010-12-11 09:54
Assigned ToEchelon9 
PlatformOSOS Version
Product Version3.6.11 
Target VersionFixed in Version3.6.12 
Summary0001991: Ship assigned to attack its own wing causes crash with invalid debugging info
DescriptionWhile the crash itself may be valid (even though the ships in the wing are traitors) the assert is not producing a valid call stack. This is all it give you:

     [Frames below may be incorrect and/or missing, no symbols loaded for ntdll.dll]
> fs2_open_3_6_11d.exe!debug_int3(char * file=0x3b020f2e, int line=243788020) Line 760 + 0x8 bytes C++


- file 0x3b020f2e <Bad Ptr> char *
            CXX0030: Error: expression cannot be evaluated
        line 243788020 int
Additional Information3.6.11 r5596. Pretty sure this worked fine (the debug stack that is) in builds about an month ago when I hit the same error in the same mission. Bug apparently wasn't fixed yet and I hit it again today when I updated the campaign I was testing and overwrote my changes. Attaching simple FS2 mission that causes the crash. Using VS2008.
TagsNo tags attached.
Attached Files? 1traitorwing.fs2 (5,860) 2009-09-14 04:54

2010-12-11 09:54   
This now is handled by an Assert() on aicode.cpp:1331

It is correctly something to report in Debug, because ship "test 1" is set to attack wing "test"; thereby attacking itself and "test 2" (being both of the members of wing "test").

Retail plays through fine.

Issue History
2009-09-14 04:54FUBAR-BDHRNew Issue
2009-09-14 04:54FUBAR-BDHRFile Added: 1traitorwing.fs2
2010-12-11 09:54Echelon9Note Added: 0012544
2010-12-11 09:54Echelon9Statusnew => resolved
2010-12-11 09:54Echelon9Fixed in Version => 3.6.12
2010-12-11 09:54Echelon9Resolutionopen => fixed
2010-12-11 09:54Echelon9Assigned To => Echelon9