0
May 20, 2013, 02:10:04 AM   
*
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
 

- Shoutbox

Pages: [1]
  Print  
Author Topic: game crashes? "DEBUG: Update for non-existant unit"  (Read 1387 times)
0 Members and 1 Guest are viewing this topic.
eric235u
Recruit
*
Posts: 2


WWW
« on: September 15, 2007, 11:05:27 PM »

hi all.  netpanzer has started crashing on me.  i join a game then almost immediately it crashes.  this is on fedora 7 x86_64.  i only use the fedora repository.  i've tried reinstalling several times and deleting all the .netpanzer files but no luck.  thanks for any tips.  here's the log file.

Code:
2007-09-15 16:47:24 Log file open
2007-09-15 16:47:24 Cleaning old log files
2007-09-15 16:47:24 couldn't read game configuration: couldn't open file 'config/netpanzer.ini' for reading: No such file or directory
2007-09-15 16:47:24 Using default config. (this is normal on first startup)
2007-09-15 16:47:24 Initializing sound system.
2007-09-15 16:47:24 Couldn't find any music in 'sound/music/'
2007-09-15 16:47:24 Initializing video mode
2007-09-15 16:47:25 Loading maps.
2007-09-15 16:47:51 DEBUG: SocketBase:: Create [udp:8] socket
2007-09-15 16:47:51 DEBUG: SocketBase:: Create [tcp:9] socket
2007-09-15 16:47:51 DEBUG: SocketBase:: Create [tcp:10] socket
2007-09-15 16:47:51 DEBUG: SocketBase:: Create [tcp:11] socket
2007-09-15 16:47:51 DEBUG: SocketManager:: Adding socket [11,00ff4880]
2007-09-15 16:47:51 DEBUG: SocketManager:: Adding socket [10,00ff4790]
2007-09-15 16:47:51 DEBUG: SocketManager:: Adding socket [9,00fb4e60]
2007-09-15 16:47:51 DEBUG: SocketManager:: Adding socket [8,00fef890]
2007-09-15 16:47:51 DEBUG: SocketManager:: Setting socket [8,00fef890] to read
2007-09-15 16:47:51 DEBUG: SocketManager:: Setting socket [9,00fb4e60] to write
2007-09-15 16:47:51 DEBUG: SocketManager:: Setting socket [10,00ff4790] to write
2007-09-15 16:47:51 DEBUG: SocketManager:: Setting socket [11,00ff4880] to write
2007-09-15 16:47:51 MASTERSERVER Connected [83.246.96.51]
2007-09-15 16:47:51 MASTERSERVER Disconected [83.246.96.51]
2007-09-15 16:47:51 DEBUG: SocketBase:: Closing [9] socket
2007-09-15 16:47:51 MASTERSERVER Connected [193.138.229.14]
2007-09-15 16:47:51 MASTERSERVER Disconected [193.138.229.14]
2007-09-15 16:47:51 DEBUG: SocketBase:: Closing [10] socket
2007-09-15 16:47:51 DEBUG: SocketManager:: Removing socket [10,00ff4790]
2007-09-15 16:47:51 DEBUG: SocketManager:: Removing socket [9,00fb4e60]
2007-09-15 16:47:51 DEBUG: SocketManager:: Setting socket [8,00fef890] to read
2007-09-15 16:47:51 DEBUG: SocketManager:: Setting socket [11,00ff4880] to write
2007-09-15 16:47:51 MASTERSERVER Connected [82.195.156.186]
2007-09-15 16:47:52 Server IP received: [213.35.164.6:3030]
2007-09-15 16:47:52 Querying server [213.35.164.6:3030]
2007-09-15 16:47:52 Server IP received: [69.12.141.72:3040]
2007-09-15 16:47:52 Querying server [69.12.141.72:3040]
2007-09-15 16:47:52 Server IP received: [216.99.214.19:3030]
2007-09-15 16:47:52 Querying server [216.99.214.19:3030]
2007-09-15 16:47:52 Server IP received: [62.147.198.99:3030]
2007-09-15 16:47:52 Querying server [62.147.198.99:3030]
2007-09-15 16:47:52 Server IP received: [213.133.102.222:3031]
2007-09-15 16:47:52 Querying server [213.133.102.222:3031]
2007-09-15 16:47:52 Server IP received: [84.160.121.148:3030]
2007-09-15 16:47:52 Server IP received: [200.147.78.99:3030]
2007-09-15 16:47:52 DEBUG: SocketBase:: Closing [11] socket
2007-09-15 16:47:52 DEBUG: SocketManager:: Removing socket [11,00ff4880]
2007-09-15 16:47:52 DEBUG: SocketManager:: Setting socket [8,00fef890] to read
2007-09-15 16:47:52 Querying server [200.147.78.99:3030]
2007-09-15 16:47:52 Querying server [84.160.121.148:3030]
2007-09-15 16:47:52 Stopping querys to servers, no more servers
2007-09-15 16:47:52 DEBUG: SocketBase:: Closing [8] socket
2007-09-15 16:47:52 DEBUG: SocketManager:: Removing socket [8,00fef890]
2007-09-15 16:48:15 Trying to join server '69.12.141.72:3040'.

2007-09-15 16:48:15 DEBUG: SocketBase:: Create [tcp:8] socket
2007-09-15 16:48:15 DEBUG: SocketManager:: Adding socket [8,00fef890]
2007-09-15 16:48:15 DEBUG: SocketManager:: Setting socket [8,00fef890] to write
2007-09-15 16:48:15 ClientSocket:: Connected to socket
2007-09-15 16:48:15 Lobby: Link to Server Established
2007-09-15 16:48:15 Lobby: Protocol Version: 1019
2007-09-15 16:48:15 Lobby: Connecting ...
2007-09-15 16:48:16 Lobby: Loading Game Data ...
2007-09-15 16:48:16 Lobby: Loading Game Data ... (4%)
2007-09-15 16:48:16 Lobby: Loading Game Data ... (9%)
2007-09-15 16:48:16 Lobby: Loading Game Data ... (14%)
2007-09-15 16:48:16 Lobby: Loading Game Data ... (19%)
2007-09-15 16:48:16 Lobby: Loading Game Data ... (24%)
2007-09-15 16:48:16 Lobby: Loading Game Data ... (29%)
2007-09-15 16:48:16 Lobby: Loading Game Data ... (34%)
2007-09-15 16:48:16 Lobby: Loading Game Data ... (39%)
2007-09-15 16:48:16 Lobby: Loading Game Data ... (44%)
2007-09-15 16:48:16 Lobby: Loading Game Data ... (49%)
2007-09-15 16:48:16 Lobby: Loading Game Data ... (54%)
2007-09-15 16:48:16 Lobby: Loading Game Data ... (59%)
2007-09-15 16:48:16 Lobby: Loading Game Data ... (64%)
2007-09-15 16:48:16 Lobby: Loading Game Data ... (69%)
2007-09-15 16:48:16 Lobby: Loading Game Data ... (74%)
2007-09-15 16:48:16 Lobby: Loading Game Data ... (79%)
2007-09-15 16:48:16 Lobby: Loading Game Data ... (84%)
2007-09-15 16:48:17 Lobby: Loading Game Data ... (89%)
2007-09-15 16:48:17 Lobby: Loading Game Data ... (94%)
2007-09-15 16:48:17 Lobby: Loading Game Data ... (99%)
2007-09-15 16:48:17 Lobby: Loading Game Data ... (100%)
2007-09-15 16:48:17 Lobby: Synchronizing Player Info ...
2007-09-15 16:48:17 Lobby: Synchronizing Player Info ... (83%)
2007-09-15 16:48:18 Lobby: Synchronizing Player Info ... (100%)
2007-09-15 16:48:18 Lobby: Synchronizing Game Elements ...
2007-09-15 16:48:18 DEBUG: Update for non-existant unit: 50152
2007-09-15 16:48:18 DEBUG: Update for non-existant unit: 50182
2007-09-15 16:48:18 DEBUG: Update for non-existant unit: 50172
2007-09-15 16:48:18 DEBUG: Update for non-existant unit: 50183
2007-09-15 16:48:18 DEBUG: Update for non-existant unit: 50158
2007-09-15 16:48:18 DEBUG: Update for non-existant unit: 50186
2007-09-15 16:48:18 DEBUG: Update for non-existant unit: 50167
2007-09-15 16:48:18 DEBUG: Update for non-existant unit: 50169
2007-09-15 16:48:18 DEBUG: Update for non-existant unit: 50164
2007-09-15 16:48:18 DEBUG: Update for non-existant unit: 50179
2007-09-15 16:48:18 DEBUG: Update for non-existant unit: 50189
2007-09-15 16:48:18 DEBUG: Update for non-existant unit: 50188
2007-09-15 16:48:18 DEBUG: Update for non-existant unit: 50173
2007-09-15 16:48:18 DEBUG: Update for non-existant unit: 50174
2007-09-15 16:48:18 DEBUG: Update for non-existant unit: 50178
2007-09-15 16:48:18 DEBUG: Update for non-existant unit: 50175
2007-09-15 16:48:18 DEBUG: Update for non-existant unit: 50182
2007-09-15 16:48:18 DEBUG: Update for non-existant unit: 50176
2007-09-15 16:48:18 DEBUG: Update for non-existant unit: 50183
2007-09-15 16:48:18 DEBUG: Update for non-existant unit: 50177
2007-09-15 16:48:18 DEBUG: Update for non-existant unit: 50186
2007-09-15 16:48:18 DEBUG: Update for non-existant unit: 50189
2007-09-15 16:48:18 DEBUG: Update for non-existant unit: 50185
2007-09-15 16:48:18 DEBUG: Update for non-existant unit: 50181
2007-09-15 16:48:18 Lobby: Synchronizing Game Elements ... (100%)
2007-09-15 16:48:18 Lobby: Game Synchronized
2007-09-15 16:48:19 DEBUG: C: eric235u has joined the game.
2007-09-15 16:48:31 DEBUG: C: Sindrome has joined the game.
2007-09-15 16:48:31 DEBUG: C: 'Giessen' has been occupied by 'Player762'
2007-09-15 16:48:43 Closing logfile.
Logged
krom
Administrator
Sergeant
*****
Posts: 493



« Reply #1 on: September 16, 2007, 06:12:11 AM »

Hi, the "Update for non-existant unit" is not a problem, it can appear when you connects to a server and receive some sync message from a unit (tank) that still is not in your list, nothing to worry about.

About the error, i have check the code, and I think there is only one possibility to end the game like that:
Quote
2007-09-15 16:48:43 Closing logfile.

There should be more messages in a normal shutdown of the game. My bet is that netpanzer is receiving a signal.

Open a terminal and run the game from it (i guess just run "netpanzer" or "netpanzer -g" to see debug messages), connect to a server and when the game exit, in the terminal window you should be able to see something like:
Quote
Received signal SIGHUP(1)
aborting and trying to shutdown.
2007-09-16 12:01:57 Closing logfile.

Maybe in your case the signal name (SIGHUP) is different, i did this one by killing the game from another terminal.

Post here once you have this information.

btw, do you know how to/are you able to compile programs?
Logged

The rabbit doesn't fly alone
eric235u
Recruit
*
Posts: 2


WWW
« Reply #2 on: September 26, 2007, 10:50:55 PM »

hi and thanks for your reply.  here's some information.

Code:
[eric@firedragon ~]$ netpanzer
2007-09-26 16:46:58 MASTERSERVER Connected [83.246.96.51]
2007-09-26 16:46:58 MASTERSERVER Disconected [83.246.96.51]
2007-09-26 16:46:58 MASTERSERVER Connected [193.138.229.14]
2007-09-26 16:46:58 MASTERSERVER Disconected [193.138.229.14]
2007-09-26 16:46:58 MASTERSERVER Connected [82.195.156.186]
2007-09-26 16:46:58 Server IP received: [84.160.119.65:3030]
2007-09-26 16:46:58 Querying server [84.160.119.65:3030]
2007-09-26 16:46:58 Server IP received: [71.213.115.250:3030]
2007-09-26 16:46:58 Querying server [71.213.115.250:3030]
2007-09-26 16:46:58 Server IP received: [216.99.214.19:3030]
2007-09-26 16:46:58 Querying server [216.99.214.19:3030]
2007-09-26 16:46:58 Server IP received: [83.246.96.51:3030]
2007-09-26 16:46:58 Querying server [83.246.96.51:3030]
2007-09-26 16:46:58 Server IP received: [69.12.141.72:3040]
2007-09-26 16:46:58 Querying server [69.12.141.72:3040]
2007-09-26 16:46:58 Server IP received: [213.133.102.222:3030]
2007-09-26 16:46:58 Server IP received: [213.35.167.176:3030]
2007-09-26 16:46:58 Server IP received: [77.132.255.204:3030]
2007-09-26 16:46:58 Querying server [77.132.255.204:3030]
2007-09-26 16:46:58 Querying server [213.35.167.176:3030]
2007-09-26 16:46:58 Querying server [213.133.102.222:3030]
2007-09-26 16:47:02 ClientSocket:: Connected to socket
Received signal SIGSEGV(11)
aborting and trying to shutdown.
Segmentation fault
[eric@firedragon ~]$

Quote
btw, do you know how to/are you able to compile programs?

i can if necessary.

thanks again.

Logged
krom
Administrator
Sergeant
*****
Posts: 493



« Reply #3 on: September 29, 2007, 02:47:39 AM »

Of all the possible signals had to be THAT one. It going to be somewhat difficult because i don't have access to a 64 bit machine. I'm in process of installing another distro (centos), after that will put qemu into work (i think it can emulate 64 bit architecture) and install fedora 7 onto it, i need to use gdb to be able to 'see'.

One thing that could help is to run netpanzer in gdb and after the crash (yes this is a real crash) run 'bt' to get a backtrace and see which function creates the problem.

The information in your /proc/cpuinfo could be usefull (to know exactly what cpu is running).
The library version that netpanzer is linked is too useful maybe a "ldd `which netpanzer`" could get that information.

And i'm just thinking, maybe the netpanzer version you are using is compiled for 32 bit and causes the problem in 64 bit cpu? could you compile the game (from svn or from source package) and try again?

some quick compilation instructions:
Code:
# ./configure
# jam
# ./netpanzer
the last line will run netpanzer, you don't need to do a "jam install" and i never do.

if you download from svn you may need to do this first:
Code:
# sh autogen.sh
Logged

The rabbit doesn't fly alone
Pages: [1]
  Print  
 
Jump to:  

Theme by m3talc0re. Powered by SMF 1.1.16 | SMF © 2006-2008, Simple Machines MySQL | PHP | XHTML | CSS
Back To Top