games:tools:steam

dependencies for steam

Leap 16.0 dropped 32-bit binaries, so we rebuild them here to make it work natively again. based on https://lists.opensuse.org/archives/list/factory@lists.opensuse.org/thread/2UJYYHHCYU3WBYP34RRAFQ2TNFGV72CY/ https://download.opensuse.org/repositories/games:/tools:/steam/16.0/ openSUSE:Leap:16.0

openSUSE Leap 16.0 based on SLFO

Leap 16.0 based on SLES 16.0 (specifically SLFO:1.2) https://download.opensuse.org/distribution/leap/16.0/repo/oss/ openSUSE:Backports:SLE-16.0

Community packages for SLE-16.0

Community packages for SLE-16.0 https://download.opensuse.org/repositories/openSUSE:/Backports:/SLE-16.0/standard/ SUSE:SLFO:1.2

SLFO 1.2 (the base for openSUSE 16.0 and SLES 16.0)

https://download.opensuse.org/repositories/SUSE:/SLFO:/1.2/standard/ valgrind

Memory Management Debugger

Valgrind checks all memory operations in an application, like read, write, malloc, new, free, and delete. Valgrind can find uses of uninitialized memory, access to already freed memory, overflows, illegal stack operations, memory leaks, and any illegal new/malloc/free/delete commands. Another program in the package is "cachegrind," a profiler based on the valgrind engine. To use valgrind you should compile your application with "-g -O0" compiler options. Afterwards you can use it with: valgrind --tool=memcheck --sloppy-malloc=yes --leak-check=yes --db-attach=yes my_application, for example. More valgrind options can be listed via "valgrind --help". There is also complete documentation in the /usr/share/doc/packages/valgrind/ directory. A debugged application runs slower and needs much more memory, but is usually still usable. Valgrind is still in development, but it has been successfully used to optimize several KDE applications.