If the module is not giving you any useful error information then you have several
courses of action. You should consult the documentation for the module.
If that is unhelpful then contact the supplier. Otherwise you are reduced to tracing the kernel calls.
Tracing the kernel calls should give you the exact errors and object names if the
problem is related to permissions, as you suspect. You will need a tool such as truss (on Sun)
or strace (on Linux, and others). Display the process PID ($$), or write it to a file, then
pause your process just before the shared object is created. Then attach truss or strace to
the process using the -p option. You will need to be signed on as the same userid, or root.
Now allow the application to continue. Once you get sufficient information then kill the truss/strace using <CTRL>C. If there is
too much data output (and there often is) then use the -o option to save it to a file for
later analysis.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.