protonscr

steamcmd.sh segfaults after first launch

steamclosed
ValveSoftware/steam-for-linux#3914 · opened 2015-07-05 by draeath · updated 2015-07-05 · 1 comments · github
Ddraeath 2015-07-05 github

Fresh debian jessie amd64 installation in a virtualbox VM. Running steamcmd as a local user.

The first time launching steamcmd works fine - it downloads stuff, and I'm able to log in anonymous and run "app_update 237410" - all seems to behave as it should. However, any subsequent runs of steamcmd.sh immediately segfault as such (I have added "set -x" to enable verbose shell output)

steam@pandora:~/steamcmd$ ./steamcmd.sh
++ cd .
++ echo /home/steam/steamcmd
+ STEAMROOT=/home/steam/steamcmd
++ basename ./steamcmd.sh .sh
+ STEAMCMD=steamcmd
++ uname
+ UNAME=Linux
+ '[' Linux == Linux ']'
+ STEAMEXE=/home/steam/steamcmd/linux32/steamcmd
+ PLATFORM=linux32
+ export LD_LIBRARY_PATH=/home/steam/steamcmd/linux32:
+ LD_LIBRARY_PATH=/home/steam/steamcmd/linux32:
+ ulimit -n 2048
+ MAGIC_RESTART_EXITCODE=42
+ '[' '' == gdb ']'
+ '[' '' == cgdb ']'
+ /home/steam/steamcmd/linux32/steamcmd
./steamcmd.sh: line 36:  8039 Segmentation fault      $DEBUGGER "$STEAMEXE" "$@"
+ STATUS=139
+ '[' 139 -eq 42 ']'
+ exit 139

I'm not sure what else I can supply, as this doesn't give very much to go by.

Ddraeath 2015-07-05 github

invalid - not sure of the cause but I have a silent filesystem corruption problem with this VM and i'm 99% certain this behavior was just what exposed it.

Nothing extracted yet.