If Memory_alloc fails, how to prevent error from being raised?

Jianyi Bao

Other Parts Discussed in Thread: SYSBIOS

Hi,

I am using "tirtos_tivac_2_00_01_23" and CCS6. Now I defined a HeapMem in .cfg file, and when Memory_alloc fails (not enough memory for example), I don't want an error to be erased (print some error message and terminate the program). Instead, I think this is normal and my code will deal with it.

I have read some threads also regarding this, and the idea usually is to modify global assert or error handling policy. This is not what I want, because I want to keep assert and error handling woking as what they are now on other code. I simply want to suspend the error in calling Memory_alloc and Memory_free, that is, I need a seperate error policy for Memory management.

Is there any idea? Thank you very much.

Currently my error module settings are:

Error hook: ti.sysbios.BIOS.errorRaiseHook

Max error nesting: 16

Error policy: UNWIND

Error policy hook: xdc.runtime.Error.policyDefault

Logger: null

over 9 years ago

0 Alan DeMars over 9 years ago

TI__Mastermind 30830 points

If you pass an Error_Block to Memory_alloc() rather than NULL, then instead of raising an Error, Memory_alloc() will fill in the Error_Block with error info and return.

The application code can then check the Error Block for errors using this code:

Error_Block eb;

buf = Memory_alloc(heap, 0x1000, 0, &eb);

    if (Error_check(&eb)) {
        do something meaningful here
    }

Alan

0 Jianyi Bao over 9 years ago in reply to Alan DeMars

Expert 2220 points

Hi,

Thanks. It woks now. I think the code should be:

Error_Block eb;

Error_init(&eb);

buf = Memory_alloc(heap, 0x1000, 0, &eb);

0 Alan DeMars over 9 years ago in reply to Jianyi Bao

TI__Mastermind 30830 points

OOPS! Sorry about that. A rookie mistake made by a veteran. I'm ashamed :-)

Alan

Processors

Processors forum

If Memory_alloc fails, how to prevent error from being raised?