use on shared library

use on shared library

I'm using TBB 2.1 on Centos 5.2 64-bit to build a shared library built
with gcc 4.1.2 which is loaded as a plugin by
a commercial application (no debug build). Is it possible to use Inspector on the library while it is running under the control of
the application? I would use the trial to test it, but company policy
currently makes this difficult.

Note that if symbol information and source are not available, all problems still will be reported. But there is no line No. info (use module's offset instead) in "Source" of "Code Locations" of the report, also you can't do "View Source".