Segment Fault Crash

For problems with the game

Moderators: jelco, bert_the_turtle, Chris, Icepick, Rkiver, Punisher Bass

2pacalypse
level0
Posts: 4
Joined: Fri May 18, 2007 5:19 pm

Segment Fault Crash

Postby 2pacalypse » Sat May 19, 2007 8:01 am

I'm experiencing a weird "Segment Fault". the crash appears about 2-3 minutes after I start the game, out of the blue. and if I run the game via terminal all it writes is the regular load screen and then "Segment fault" heres the terminal output

Code: Select all

=============================
=                           =
=        U P L I N K        =
=                           =
=        Version 1.54       =
=     - R E L E A S E -     =
=                           =
=============================

Version 1.54 (RELEASE)
Compiled on Nov 16 2006 at 20:46:23
(code-C)(code-M)(code-T)
Segmentation fault


now the weird thing is that this crash doesn't have any crash/debug log at all. I've attempted to reinstall the game several times each time I attempted a different version but alas its still crashing

I am Running Debian Etch (4.0),Uplink 1.54
User avatar
frenchfrog
level5
level5
Posts: 2572
Joined: Sun Sep 22, 2002 7:11 pm
Location: Quebec

Postby frenchfrog » Sat May 19, 2007 5:11 pm

1) Try the latest patch (currently 1.55), it's more verbose.

2) Check for the ~/.uplink/debug.log file.

3) Try with a new agent.
The Ultimate Uplink Guide (for any question on Uplink)
Latest Uplink Patch
2pacalypse
level0
Posts: 4
Joined: Fri May 18, 2007 5:19 pm

Postby 2pacalypse » Sun May 20, 2007 4:17 pm

1)ok upgraded and I ran the game twice(but no segment fault errors), first time it was crash right at the agent login screen, heres the first attempt in the terminal

Code: Select all

=============================
=                           =
=        U P L I N K        =
=                           =
=        Version 1.55       =
=     - R E L E A S E -     =
=                           =
=============================

Version 1.55 (RELEASE)
Compiled on Mar 19 2007 at 13:34:53
(code-C)(code-M)(code-T)

An Uplink Internal Error has occured: segmentation violation (SIGSEGV)

An (unrecognised) Uplink Internal Error has occured
===================================================
See the /home/kronos/.uplink/debug.log file for more informations on the error

and heres the related debug.log file (which btw magiclly appeared in this update but was not present before)

Code: Select all

===============================================
NEW GAME     15:3, 21/5/2007
===============================================
Version : 1.55
RELEASE
Linux Build
Version 1.55 (RELEASE)
Compiled on Mar 19 2007 at 13:34:53
(code-C)(code-M)(code-T)
Loading uplink options from /home/kronos/.uplink/options...success

Successfully loaded data archive data.dat
Successfully loaded data archive graphics.dat
Successfully loaded data archive loading.dat
Successfully loaded data archive sounds.dat
Successfully loaded data archive music.dat
Successfully loaded data archive fonts.dat
Successfully loaded data archive patch.dat
Successfully loaded data archive patch2.dat
Successfully loaded data archive patch3.dat
Saving uplink options to /home/kronos/.uplink/options...success
Saving uplink options to /home/kronos/.uplink/options...success
Compiled with SDL_mixer version: 1.2.7
Running with SDL_mixer version: 1.2.7
New patch Detected!
Old version = 131
New version = 155


An Uplink Internal Error has occured: segmentation violation (SIGSEGV)

An (unrecognised) Uplink Internal Error has occured
===================================================
============== B E G I N  C O R E  D U M P =================
retAddress = 0x804f43b
retAddress = 0x80f9b76
retAddr2222ess = 0xb7f84420
============== E N D  C O R E  D U M P =====================

and in the second try, I managed to play for a few minutes, barely enough for one mainframe hack. heres the terminal

Code: Select all

=============================
=                           =
=        U P L I N K        =
=                           =
=        Version 1.55       =
=     - R E L E A S E -     =
=                           =
=============================

Version 1.55 (RELEASE)
Compiled on Mar 19 2007 at 13:34:53
(code-C)(code-M)(code-T)

An Uplink Internal Error has occured: segmentation violation (SIGSEGV)

An (unrecognised) Uplink Internal Error has occured
===================================================
See the /home/kronos/.uplink/debug.log file for more informations on the error


and heres the debug.log

Code: Select all

===============================================
NEW GAME     15:4, 21/5/2007
===============================================
Version : 1.55
RELEASE
Linux Build
Version 1.55 (RELEASE)
Compiled on Mar 19 2007 at 13:34:53
(code-C)(code-M)(code-T)
Loading uplink options from /home/kronos/.uplink/options...success

Successfully loaded data archive data.dat
Successfully loaded data archive graphics.dat
Successfully loaded data archive loading.dat
Successfully loaded data archive sounds.dat
Successfully loaded data archive music.dat
Successfully loaded data archive fonts.dat
Successfully loaded data archive patch.dat
Successfully loaded data archive patch2.dat
Successfully loaded data archive patch3.dat
Saving uplink options to /home/kronos/.uplink/options...success
Saving uplink options to /home/kronos/.uplink/options...success
Compiled with SDL_mixer version: 1.2.7
Running with SDL_mixer version: 1.2.7
New patch Detected!
Old version = 131
New version = 155

Loading profile from /home/kronos/.uplink/Instomnia.usr...HUDInterface::HighlightToolbarButton, invalid button : hud_analyser
success
Loading LAN from data/lans/sample.txt...[Already Loaded]
Saving profile to /home/kronos/.uplink/Instomnia.tmp...success. Moving profile to /home/kronos/.uplink/Instomnia.usr...success
Saving profile to /home/kronos/.uplink/Instomnia.tmp...success. Moving profile to /home/kronos/.uplink/Instomnia.usr...success
Saving profile to /home/kronos/.uplink/Instomnia.tmp...success. Moving profile to /home/kronos/.uplink/Instomnia.usr...success
Saving profile to /home/kronos/.uplink/Instomnia.tmp...success. Moving profile to /home/kronos/.uplink/Instomnia.usr...success
Saving profile to /home/kronos/.uplink/Instomnia.tmp...success. Moving profile to /home/kronos/.uplink/Instomnia.usr...success
Saving profile to /home/kronos/.uplink/Instomnia.tmp...success. Moving profile to /home/kronos/.uplink/Instomnia.usr...success
Saving profile to /home/kronos/.uplink/Instomnia.tmp...success. Moving profile to /home/kronos/.uplink/Instomnia.usr...success

An Uplink Internal Error has occured: segmentation violation (SIGSEGV)

An (unrecognised) Uplink Internal Error has occured
===================================================
============== B E G I N  C O R E  D U M P =================
retAddress = 0x804f43b
retAddress = 0x80f9b76
retAddress = 0xb7fb9420
============== E N D  C O R E  D U M P =====================


Just to note, I already tried 5 diffrent agent, same prob in each one,I tried to make a new one after this update and it's still the same thing
User avatar
frenchfrog
level5
level5
Posts: 2572
Joined: Sun Sep 22, 2002 7:11 pm
Location: Quebec

Postby frenchfrog » Sun May 20, 2007 7:14 pm

2pacalypse wrote:

Code: Select all

===================================================
============== B E G I N  C O R E  D U M P =================
retAddress = 0x804f43b
retAddress = 0x80f9b76
retAddress = 0xb7fb9420
============== E N D  C O R E  D U M P =====================


From those addresses it seems Uplink is crashing outside it's _own_ memory space. Which means a driver could be at fault.
2pacalypse
level0
Posts: 4
Joined: Fri May 18, 2007 5:19 pm

Postby 2pacalypse » Mon May 21, 2007 7:48 am

err can you specify more? is it a bad nvidia driver or something else
User avatar
frenchfrog
level5
level5
Posts: 2572
Joined: Sun Sep 22, 2002 7:11 pm
Location: Quebec

Postby frenchfrog » Mon May 21, 2007 3:42 pm

Near impossible to tell, Uplink is not instrumented to catch OS bugs.
2pacalypse
level0
Posts: 4
Joined: Fri May 18, 2007 5:19 pm

Postby 2pacalypse » Mon May 21, 2007 3:59 pm

ok, can you tell is where I can find a program or a way to catch this OS bug?

Return to “Bug Reports”

Who is online

Users browsing this forum: No registered users and 3 guests