Skip to content
This repository has been archived by the owner on Apr 17, 2022. It is now read-only.

crash: error |12:48:58: [moveDroidToBase] Invalid point count for path #738

Closed
wzdev-ci opened this issue Jul 20, 2009 · 11 comments
Closed

crash: error |12:48:58: [moveDroidToBase] Invalid point count for path #738

wzdev-ci opened this issue Jul 20, 2009 · 11 comments
Labels
closed component: other normal
Milestone
unspecified

Comments

@wzdev-ci
Copy link
Contributor

resolution_fixed type_bug | by stiv

Log message: error |12:48:58: [moveDroidToBase] Invalid point count for path

Log message: error |12:48:58: [moveDroidToBase] Assert in Warzone: move.c:384 (psDroid->sMove.numPoints > 0), last script event: '15 (CALL_DROID_DESTROYED)'

Issue migrated from trac:738 at 2022-04-15 19:01:44 -0700
@wzdev-ci
Copy link
Contributor Author

stiv uploaded file warzone2100.gdmp-MKMemL (11.3 KiB)

crash dump

@wzdev-ci
Copy link
Contributor Author

Per commented

Got a savegame that can reproduce it?

@wzdev-ci
Copy link
Contributor Author

Buginator commented

Something was changed in the path finding code, and it is screwing things up. I was thinking it has to do with the other patch you did for the path finding recently.

@wzdev-ci
Copy link
Contributor Author

Per commented

I haven't touched the path finding code recently. Which change do you have in mind?

@wzdev-ci
Copy link
Contributor Author

wzdev-ci commented Jul 26, 2009 •
edited

Buginator commented

Replying to Warzone2100/old-trac-import#738 (comment:3):

I haven't touched the path finding code recently. Which change do you have in mind?

My 'recent' means the last code changes you did, I guess it may also can be the 'orders' change as well.

The units either get new orders, and the path list is empty, or the list gets empty by something.

When I come back, I will try to narrow it down a bit more, since the above is only really a guess.

@wzdev-ci
Copy link
Contributor Author

nobby commented

Here's a move.c:384 error and a savegame file that will reproduce it. I built the binary.

To reproduce: Open 'Test14' savegame. System will crash.

-----------------

Error occured on Monday, July 27, 2009 at 21:42:49.

Program: E:\Dev\Warzone2100\trunk\Warzone2100.exe(warzone2100)
Command line: "E:\Dev\Warzone2100\trunk\Warzone2100.exe" 
Version: Version TRUNK [0] - Built Jul 26 2009 - DEBUG
Distributor: UNKNOWN
Compiled on: Jul 26 2009 21:35:28
Compiled by: GCC 3.4.5 (mingw-vista special [3])
Executed on: Mon Jul 27 21:27:16 2009

Pointers: 32bit

Compiled against PhysicsFS version: 1.0.1
Running with PhysicsFS version: 1.0.1

Misc Data:
[09:27:16]OpenGL Vendor : NVIDIA Corporation
[09:27:16]OpenGL Renderer : Quadro FX 1400/PCI/SSE2/3DNOW!
[09:27:16]OpenGL Version : 2.1.2
[09:27:17]OpenAL Vendor: Creative Labs Inc.
[09:27:17]OpenAL Version: 1.1
[09:27:17]OpenAL Renderer: Software
[09:27:17]Using language: System locale
[09:27:29]Current Level/map is Sk-Basingstoke-T3


E:\Dev\Warzone2100\trunk\Warzone2100.exe caused a Breakpoint at location 77c35b61 in module C:\WINDOWS\system32\msvcrt.dll.

Log message: error   |09:42:46: [moveDroidToBase] Invalid point count for path
Log message: error   |09:42:46: [moveDroidToBase] Assert in Warzone: move.c:384 (psDroid->sMove.numPoints > 0), last script event: 'N/A'

Registers:
eax=00000004 ebx=00000003 ecx=00009434 edx=00280000 esi=77c12d25 edi=00000001
eip=77c35b61 esp=0022f568 ebp=0022f8a8 iopl=0         nv up ei pl zr na po nc
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00200246

Call stack:
77C35B61  C:\WINDOWS\system32\msvcrt.dll:77C35B61  _assert
004B736F  E:\Dev\Warzone2100\trunk\Warzone2100.exe:004B736F
004B766A  E:\Dev\Warzone2100\trunk\Warzone2100.exe:004B766A
004BE230  E:\Dev\Warzone2100\trunk\Warzone2100.exe:004BE230
00440754  E:\Dev\Warzone2100\trunk\Warzone2100.exe:00440754
004A2C5C  E:\Dev\Warzone2100\trunk\Warzone2100.exe:004A2C5C
004A54EE  E:\Dev\Warzone2100\trunk\Warzone2100.exe:004A54EE
004A58CF  E:\Dev\Warzone2100\trunk\Warzone2100.exe:004A58CF
004A605E  E:\Dev\Warzone2100\trunk\Warzone2100.exe:004A605E
0063E75A  E:\Dev\Warzone2100\trunk\Warzone2100.exe:0063E75A
0063E942  E:\Dev\Warzone2100\trunk\Warzone2100.exe:0063E942
0063E218  E:\Dev\Warzone2100\trunk\Warzone2100.exe:0063E218
0040124B  E:\Dev\Warzone2100\trunk\Warzone2100.exe:0040124B
004012B8  E:\Dev\Warzone2100\trunk\Warzone2100.exe:004012B8
7C817077  C:\WINDOWS\system32\kernel32.dll:7C817077  RegisterWaitForInputIdle

@wzdev-ci
Copy link
Contributor Author

nobby uploaded file Test14.zip (314.0 KiB)

Savegame that will produce move.c:384 crash

@wzdev-ci
Copy link
Contributor Author

nobby uploaded file Warzone2100.exe.bz2 (4866.5 KiB)

Binary that produced the crash

@wzdev-ci
Copy link
Contributor Author

Per changed status from new to closed

@wzdev-ci
Copy link
Contributor Author

Per set resolution to fixed

@wzdev-ci
Copy link
Contributor Author

Per commented

(In [7916]) 2.2: Fix crash length overflow by capping path lengths to max 255 nodes. Closes #738

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
closed component: other normal
Projects
None yet
Milestone
unspecified
Development

No branches or pull requests
1 participant
@wzdev-ci