• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 439 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

[Sys/Bios] HeapBuf_free Error Handling

Alex
Expert 2430 points
Other Parts Discussed in Thread: SYSBIOS

Is there any way (some SysBios configuration setting I hope) to make HeapBuf_free() fail silently instead of throwing an exception and causing the system to abort?

  • 0
    TI__Mastermind 20480 points

    Hi Alex,

    which version of SYS/BIOS and XDCtools are you using?

    You can disable assert statements. See the xdc/runtime/Diags and xdc/runtime/Assert modules here.

    Add this to your .cfg file to disable the Assert statements.

    var Assert = xdc.useModule('xdc.runtime.Assert');

    var Diags = xdc.useModule('xdc.runtime.Diags');

    var Main = xdc.useModule('xdc.runtime.Main');

    Main.common$.diags_ASSERT = Diags.ALWAYS_OFF;

    Main.common$.diags_INTERNAL = Diags.ALWAYS_OFF;

  • 0 in reply to Tom Kopriva
    Expert 2430 points

    That's interesting because I thought I already had the asserts disabled via the following...

    var BIOS         = xdc.useModule( 'ti.sysbios.BIOS'  );
    BIOS.assertsEnabled = false;

    But (1) I suppose BIOS and xdc are two different classes, and (2) I don't have that INTERNAL mask set at all.

    But, okay, thanks for your speedy reply!  Very appreciated!! I'll give that a shot.

  • 0 in reply to Alex
    Expert 2430 points

    Well, after further testing, it looks like I was chasing a false lead.  It turns out that my BIOS.assertsEnabled = false was enough to stop the exceptions.  It was only in debug mode that I got the exceptions (where I have BIOS.assertsEnabled = true).  In release mode, nada.

    I still like your approach, though, so I am leaving it in.  It seems more thorough, so thanks again!