Differences between version 2 and previous revision of LD_DEBUG.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 2 | Last edited on Friday, June 13, 2003 8:50:13 pm | by JohnMcPherson | Revert |
| Older page: | version 1 | Last edited on Friday, June 13, 2003 8:49:00 pm | by JohnMcPherson | Revert |
@@ -1,9 +1,9 @@
The dynamic library loader used in linux (part of glibc) has some neat tricks. One of these is that you can set an environment variable called
LD_DEBUG
to show how symbols (variables and functions, for example) are resolved for a dynamic executable. This can sometimes help resolve obscure bugs where your application isn't doing what you expect (assuming it is caused by symbols being resolved differently to what you were expecting).
-
This is very useful if you get segmentation violations or aborts for a program - this can sometimes be caused by linking against the wrong version of a library. This is also a really good way to understand what happens when you run any program!
+This is very useful if you get segmentation violations or aborts for a program - this can sometimes be caused by linking against the wrong version of a library. This is also a really good way to understand what happens when you run any program!
It has some self-documentation - for the impatient, you can do
$ LD_DEBUG=help /path/to/some/dynamic/executable
eg
