Debugging into IPC-calls doesn't work properly

Clemens Eisserer

Hi,

We experience stability issues when sending Messages using IPC MessageQs over SRIO, therefore I tried to debug into IPC functions.

Although I set the build-profile to "debug", the RTSC build profile also to "debug" and appended the following lines to the rtsc-config-file:

> BIOS.libType = BIOS.LibType_Custom;
> BIOS.customCCOpts = BIOS.customCCOpts.replace("-o3", "-o0");

... when I step into an IPC function, it seems debug-symbols and source-code don't match (line-numbers, branches, etc) - even although I manually located the source of MessageQ.c within the same version of IPC I use for linking.

Any idea how I can get debug-information and source-code in sync for external libaries like IPC?

Thank you in advance, Clemens

over 12 years ago

Clemens Eisserer over 12 years ago

Expert 2430 points

Hi again,

To better illustrate my issue I've recorded a sceencast: http://youtu.be/o80h7wFjN4M

Some tips how to get debug-information and source in sync for the IPC package would be awesome ;)

Regards, Clemens

Clemens Eisserer over 12 years ago in reply to Clemens Eisserer

Expert 2430 points

Bump

Should I better ask this question in the CCS section?

Regards, Clemens

Emmanuel Trinidad - Alicea over 12 years ago in reply to Clemens Eisserer

TI__Genius 10260 points

Hi Clemens,

Sorry for the delayed response. Before we go any further, what versions of CCS, IPC and SYS/BIOS are you using?

Thanks,

-- Emmanuel

Clemens Eisserer over 11 years ago in reply to Emmanuel Trinidad - Alicea

Expert 2430 points

Hi Emmanuel,

Thanks for your response.

A collegue of mine was able to solve the debugging issue by using custom built RTSC-packages compiled with optimization disabled. He even found a way to work arround the breakage introcuced to our CCS5-project by "Bios.libType = LIbType.Custom".

Regards, Clemens

Processors

Processors forum

Debugging into IPC-calls doesn't work properly