I have both VCS (inclusing Storage Foundation) and Linux knowledge. I wish the sysInternals tool DebugView would have captured it too but it doesn't: the dynamic loader uses LdrpLogDbgPrint which is a DbgPrint variant DebugView doesn't capture and probably never will.I was wondering if someone has some additional information regarding how to setup my cluster.
That's not entirely accurate: the output is shown in regular visual studio debug console as well. Specifically, the checkbox "Show loader snaps" on the "Image file" tab (see screenshot below) is documented to ( ) ".capture detailed information about the loading and unloading of executable images and their supporting library modules and displays the data in the kernel debugger console." It is the registry key FLG_SHOW_LDR_SNAPS - which in principle you can set yourself, but it is really recommended to do it via the GUI tool gflags, packaged with WinDbg. On windows the proper tool is rather hidden. I never bothered with its various values, just set it to =all and grep the output for whatever you need. On Linux the right tool is the well documented environment variable LD_DEBUG. But when a library with the needed name was located but didn't contain the needed function - heavier artillery is needed. When needed libraries are missing entirely, strace/ProcMon can show the program failing to locate the file. Occasionally I find myself needing to peek at its operation to troubleshoot program loading.
That someone goes by many names: in windows it is sometimes called the "Loader", on linux it is sometimes called "Interpreter", but in both it is often named "dynamic linker". When a program starts, someone needs to locate all the libraries it depends on, load them into the program memory and do the necessary wiring to link the calls.
0 kommentar(er)
