I have an program that calls libcurl, and libcurl calls libgssapi_krb5.

If I want to debug calls to libcurl, then ltrace works.

But now I want to debug calls to libgssapi_krb5, then ltrace my_program does not give out anything.

  • ltrace ought to be tracing all calls to functions in libraries dynamically loaded by the process at startup. You may have problems tracing calls to libraries that were loaded into the running process by libdl. Is that how libcurl loads libgssapi_krb5? More recent versions of ltrace may be fixed (see rhn.redhat.com/errata/RHBA-2012-0926.html ) so that the -x option can be used to trace functions in dlopen'ed libraries. – Mark Plotnick Jan 9 '14 at 2:39
  • I am using 0.5.3, which does not work as wanted.... – Magicloud Jan 9 '14 at 5:43
  • A workaround might be to make a call to something, anything, in libgssapi_krb5 in your own code so that the library gets dynamically loaded at startup. – Mark Plotnick Jan 9 '14 at 11:18

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.