That "Process $PID failed to shm_open" is certainly a problem, you have shm support enabled (/run/shm mounted I think) right?
You got me there. I'm actually running SteamCMD within a Jessie i386 chroot and I only bind-mounted /dev, /sys and /proc, which worked well for quite some time (several months, it started segfaulting a few weeks ago). I changed this to a (recursive) rbind-mount (which includes /dev/shm) and it works now.
Despite my providing an apparently shm-less environment, SteamCMD shouldn't segfault.
Hello @carstenandrich, are you still experiencing this issue on an up to date system?
Closing pending feedback.
Nothing extracted yet.
The current Linux SteamCMD executable always segfaults when quitting.
Steps to reproduce:
Loading Steam API...Process $PID failed to shm_open /steam-ValveIPCSharedObjects5
This happens on an up-to-date Debian Jessie.
Output with gdb attached: