• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 100 subscribers
  • Views 632 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.

[C6713] C++ exceptions

vanmierlo
Prodigy 10 points

I can't seem to find what the C++ compiler + library for the C6713 do with exceptions.

I know that the C++ new operator can throw exceptions, but it may also just return 0. However I cannot find what the TI compiler does.

And if I have an unhandled expection, what will my code do? Will it send a message to stdout or stderr? Wil it call abort() or exit()?

B.t.w. does anyone know of a nice overview of which C++ operators and functions can throw exceptions?

Basically my problem is that my application sometimes just stops working and I find it lurking in SYS_EXITFN. That is why I expect I have an unhandled exception somewhere. But I don't see anything in my Stdout window.

 Any help is welcome,

Maarten Brock

  • 0
    TI__Mastermind 18130 points

    I do not believe that you will receive any messages in the Stdout window unless you create a custom printf() message. I don't know of any good TI-published documents discussing this, but from what I can recall C++ exception handling is not nearly as powerful as Java exception handling. I think that the C++ implementation of exceptions does not automatically throw an exception; rather, the user code must be written such to check for problems and then throw an error (e.g., if (denominator == 0) throw dividebyzeroerror();).

     

    I think that in DSP/BIOS systems there is an EXC module that can capture messages using the log message buffer, but this may be limited to C64x+ hardware. Maybe we can get someone else to come along and fill in the blanks for us.

  • 0 in reply to TimHarron
    TI__Guru*** 125430 points

    Here's Chapter 7.11 from the Compiler Reference Guide (spru187n):

    "The compiler supports all the C++ exception handling features as defined by the ISO 14882 C++
    Standard. More details are discussed in The C++ Programming Language, Third Edition by Bjarne
    Stroustrup.

    The compiler --exceptions option enables exception handling. The compiler’s default is no exception
    handling support.

    For exceptions to work correctly, all C++ files in the application must be compiled with the --exceptions
    option, regardless of whether exceptions occur in a particular file. Mixing exception-enabled object files
    and libraries with object files and libraries that do not have exceptions enabled can lead to undefined
    behavior. Also, when using --exceptions, you need to link with run-time-support libraries whose name
    contains _eh. These libraries contain functions that implement exception handling.

    Using --exceptions causes increases in code size and execution time, even if no exceptions are thrown."

    The EXC module in BIOS is limited to 64x+ only.  It's more of a "hardware thing" than a "C++ thing" though.  For example, on 64x+ architecture if you execute an illegal instruction then it will generate a hardware exception.  There is a check-box on the BIOS HWI module which allows you to enable the EXC module to automatically handle those exceptions for you.  It's a nice feature, though not related to C++ exceptions.