I never used valgrind before, so I'm into new territories with this, but I'll probably give it a try.

Thanks for your suggestion.

Update: valgrind rocks! Now I just cannot understand how come I never used it till now ... ?!

To all the fellow cowards like me (as I guess it was plain fear of yet-such-another-hard-to-use-debugging-tool that made me overlook it for so long): it's nothing to be afraid of! It's strong, but very gentle with newbies too - somewhat like Perl in this regard.

And yes, it gave me in just a few minutes the information I was trying to find for a few days already: it's an Oracle shared library that causes my headache: libclntsh.so.9.0. Now if that isn't of help, I don't know what would be...

Thanks again for pointing me this marveluous tool. I definitely became a fan of it in no time.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.