When I enable trace, why am I getting a lot of errors in APIs after “Entered DSPLINK_atExitHandler” print?
All the errors in the DSPLINK_atExitHandler can be ignored. From DSPLink v1.50 onwards, on Linux, DSPLink registers an atExit handler with Linux to take care of all cleanup (shutdown APIs) that user may have neglected to do. All DSPLink APIs check for whether anything needs to be actually done in the function, or it’s been called unnecessarily. If the application had, in fact, made all shutdown APIs as expected, each call in the atExit handler will have happened an extra time. In such cases, each API puts out error codes and possibly SET_FAILURE_REASON prints. However, since all the cleanup has already happened in normal execution, the errors in atExit handler can be ignored.
Related Questions
- I am trying to print out a postscript file and instead I get a page with errors printed on the top, or I ve looked through the log output (lpq -L) and found a postscript error message. Whats going on?
- When I enable trace, why am I getting a lot of errors in APIs after "Entered DSPLINK_atExitHandler" print?
- How can I disable or more securely enable file and print sharing?
