• Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 579 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Exceptions not always caught

Shiran Ben Israel
Intellectual 530 points
Other Parts Discussed in Thread: TCI6636K2H

Hi

I am using a code composer  6.0.1.00040 compiler 7.4.13 running on EVM TCI6636K2H.

I see the following problem.

I am throwing exceptions from one library and catching it in another.

The exception is not caught and abort is called.

I tried catch(...) and that doesn't work either.

I tried from other libraries to through and catch, and some places it works and some it doesn't catch (but as long as i don't change code the effect is consistent).

However, in one place where i did manage to catch the exception, i changed completely unrelated code (which is supposed to run much later), and suddenly the exception isn't caught.

I tried to reproduce in a small example, but there it is caught all of the time.

I made sure that Enable c++ exception handling is turned on in all libraries.

May this have anything to do with bug SDSCM00050660?

Any other flags that i am supposed to turn on?

Sincerely

Shiran

  • TI__Guru* 84225 points
    If you are able to link successfully, you are not suffering from SDSCM00050660.
    I'm not aware of any known bugs with anything like the symptoms you are describing.
    Do you have your own custom version of std::terminate?
    Make sure you have a generous heap allocated. Exception handling requires some dynamic allocation.
    What is the type of your exception object? Is it large?
    Are you using dynamic linking?
    Are you throwing between threads?
  • TI__Guru**** 244930 points

    Shiran Ben Israel said:
    I am throwing exceptions from one library and catching it in another.

    This is no different than one source file throwing an exception that is caught in another.  Both scenarios work the same way.

    Shiran Ben Israel said:
    May this have anything to do with bug SDSCM00050660?

    No.  That was an error in CCS, not the compiler.

    Shiran Ben Israel said:
    Any other flags that i am supposed to turn on?

    No.  Using --exceptions is required everywhere.  But if you get that wrong, the linker tells you.  

    Shiran Ben Israel said:
    I tried to reproduce in a small example, but there it is caught all of the time.

    This is the most unfortunate part.  Without a test case that lets us see the behavior ourselves, there is nothing we can do.

    Thanks and regards,

    -George