Mbed error info not printed with mbed-os-5.12.0

[desowin]

Description

Consider following dummy application:

int main(void)
{
    char *buf;
    do
    {
        buf = new char[1024];
    }
    while (buf);
}

As the application leaks memory, mbed error will eventually occur and on serial port there'll be information like (mbed-os-5.11.5):

++ MbedOS Error Info ++
Error Status: 0x8001011F Code: 287 Module: 1
Error Message: Operator new[] out of memory

Location: 0x80029A5
Error Value: 0x400
Current Thread: main  Id: 0x2000551C Entry: 0x8002EA3 StackSize: 0x1000 StackMem: 0x20005560 SP: 0x200064F4
For more info, visit: https://armmbed.github.io/mbedos-error/?error=0x8001011F
-- MbedOS Error Info --

However with mbed-os-5.12.0, no data is received on serial port.

I am observing the issue with 32F746GDISCOVERY board. The command I use to compile and run the application is mbed compile --target DISCO_F746NG -t GCC_ARM --flash

Issue request type

[ ] Question
[ ] Enhancement
[X] Bug

[cmonr]

...huh. That's an interesting test case.

CC @ARMmbed/mbed-os-core

[ciarmcom]

Internal Jira reference: https://jira.arm.com/browse/MBOCUSTRIA-1071

[kegilbert]

Tested on a K64F (all I had on hand at the time) with GCC_ARM on 5.11, 5.12, and master and was able to get

++ MbedOS Error Info ++
Error Status: 0x8001011F Code: 287 Module: 1
Error Message: Operator new[] out of memory
...

each time with the described code snippet. I'll try to track down a 32F746GDISCOVERY, might be something target specific.

[cmonr]

However with mbed-os-5.12.0, no data is received on serial port.

I recall seeing another issue about serial port intiialization. I wonder if this is related.

[cmonr]

Possibly related: #10344