search

ValveSoftware / steam-for-linux

Issue tracking for the Steam for Linux beta client
4.21k stars 174 forks source link

ldd log for runtime debugging #4050

Open thePalindrome opened 8 years ago

thePalindrome commented 8 years ago

Howdy, just got done smashing my head on a wall trying to figure out which libraries from the steam runtime cause my games to crash (for an example, Unturned. The game starts when launched from a shell, but when launched from steam, it crashes without leaving anything in stderr or stdout), and I think it'd be a swell idea to output either an entire ldd log, or maybe just the libraries that get pulled from the steam runtime.

I am aware that power users can edit the launch options to write an ldd log, but I think that maintaining a log for people that don't want to go through that would be rather nice.

Possible problems that I can see: Games that "launch" from a shell script i.e. World of Guns: Dissasembly. (I'm stumped on that one) Maintaining the log so that each game has only one ldd entry (use JSON for the log?)

sizeofbool commented 8 years ago

You can do this already. Just set game(tested on Unturned) launch options like this:

ldd %command% >/tmp/dumps/ldd.log

And run game from Steam Library as usual. Look inside /tmp/dumps/ldd.log for output.

thePalindrome commented 8 years ago

A "fix" that may or may not work is to set the launch options to: LD_LIBRARY_PATH=$SYSTEM_LD_LIBRARY_PATH %command% That will cause steam's runtime to not load. Use it only if you know that you have the libraries on your system!

Alas, the only way to fix all the library issues is to have the games bundle the libraries they need, or a system similar to how the win32 steam works.