Quote:
Uninitialised value was created by a stack allocation
If I understand it correctly, you have the source code of a dynamic library ( shared libray) with the name ld-2.13.so. For this, someone has created an executable file, but the source code for it is not available. When using the library a "Segmentation Fault" occurs. Valgrind reports a place where an "uninitialized value was created by a stack assignment". So the error indicates that a local variable is used which is not initialized. Often it is a pointer.
1. I would assume that such an error is indicated in the source code of the library with the appropriate compiler flags or perhaps also with splint already with the production.
2.Even if the executable is neither in source code nor in debug mode the program can be started with a debugger. If you are lucky the debugger stops at the error location, otherwise you have to work your way to the error location. Without debug code it will probably be hard to work your way to the error location.
3. As Stefan_Lang already noted, you could write your own program to test the library. It would of course help to narrow down the error so that you don't have to test every function.