Code::Blocks Forums

User forums => Using Code::Blocks => Topic started by: hagai_sela on April 30, 2009, 02:05:07 pm

Title: errors when trying to debug using intel compiler, ipp and gdb
Post by: hagai_sela on April 30, 2009, 02:05:07 pm

Hi,
I am trying to debug a program which uses intel's IPP library. I compiled my code using Intel's c++ compiler and I am trying to use gdb as a debugger (I set the toolchain accordingly).
My problem is that I get this error:

error while loading shared libraries: libippmem64t.so.6.0: cannot open shared object file: No such file or directory

I tried using gdb outside of code::blocks and it loads OK (I can use start, run, next etc). My LD_LIBRARY_PATH contains the directory which contains the missing file, so I think this has something to do with cb_console_runner not reading my environment properly. Can I configure cb_console_runner to search libraries in additional directories?

Thanks,
Hagai.

Title: Re: errors when trying to debug using intel compiler, ipp and gdb
Post by: mariocup on April 30, 2009, 04:20:37 pm

Hi hagai_sela,

I did not try it, but I think the following procedure could work.
Define LD_LIBRARY_PATH within the Code::Blocks menu Settings->Environment->Environment variables->Add
Name: LD_LIBRARY_PATH
value: <your value>

Title: Re: errors when trying to debug using intel compiler, ipp and gdb
Post by: hagai_sela on April 30, 2009, 04:51:49 pm

Quote from: mariocup on April 30, 2009, 04:20:37 pm

Hi hagai_sela,

I did not try it, but I think the following procedure could work.
Define LD_LIBRARY_PATH within the Code::Blocks menu Settings->Environment->Environment variables->Add
Name: LD_LIBRARY_PATH
value: <your value>

I tried it with and without adding to the current LD_LIBRARY_PATH (I set LD_LIBRARY_PATH to $(LD_LIBRARY_PATH):/opt/intel/Compiler/11.0/083/ipp/em64t/lib or just to /opt/intel/Compiler/11.0/083/ipp/em64t/lib). Same results.

Hagai.

Title: Re: errors when trying to debug using intel compiler, ipp and gdb
Post by: hagai_sela on May 01, 2009, 12:53:25 pm

Solved by installing the svn trunk version and running ldconfig.