Compiling with debug info on SDK 2.2

Discussion created by Marix on Sep 16, 2010
Latest reply on Sep 17, 2010 by genaganna

Is it possible to use "-g" as a compiler flag (for CPU target) on SDK 2.2? If I do there seems to be a memory leak, with clc consuming more and more memory until it finally fails to allocate more memory:

Exit code of clBuildProgram is -11.

Build log ist:

terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc

My system is openSUSE 11.2 with Catalist 10.7, 10.8 and 10.9 tried.

It seems to be ok for small source files (like hellocl), but runs into this error for larger ones.

As it works for smaller files it might be that I am using something special causing this behaviour. Did somebody else observe such a behaviour?