Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >
article

KB-0851: gdb/wdb debugger crashes if DirectAudit is enabled

Centrify DirectAudit ,   Centrify DirectControl ,   Centrify Identity Service, Mac Edition ,  

12 April,16 at 11:47 AM

Applies to: All versions of DirectAudit on Redhat 5 and HP-UX 11.00

 

Problem:

 

With Centrify DirectAudit installed and enabled, the gdb/wdb debugger tool is unable to execute the application user is debugging, instead it reports Unable to read the dynamic library list”.  The debugger works fine when DirectAudit is disabled.  However, on Redhat 5.0 this error is not seen, but instead user is unable to set breakpoints.

 

Cause:

 

gdb starts the process via the user's SHELL variable. For example, if the user's shell is: SHELL=/bin/bash, then gdb runs:  /bin/bash -c <command gdb ran with>

When Centrify DirectAudit is enabled, DirectAudit is executed instead of bash and it in turn then executes bash, which then executes the command itself.  It is this double execute which separates the process from gdb's control and prevents proper operation. 

 

Workaround:

 

Edit the value of $SHELL to an unaudited shell (i.e. instead of /bin/bash, use /bin/bash.daudit) before running gdb.  An alias or wrapper script can be used to automate this process.

 

$ SHELL=/bin/bash.daudit gdb ./myapp

Still have questions? Click here to log a technical support case, or collaborate with your peers in Centrify's Online Community.