Add Error Decoding URL to error report

[SenRamakri]

Description

Adding Error Decoding URL to error report.

Pull request type

[ ] Fix
[ ] Refactor
[ ] New target
[x] Feature
[ ] Breaking change

[cmonr]

I would suggest either adding a space in goto or replacing it with visit.

[SenRamakri]

"visit" sounds better, let me make that change.

[cmonr]

/morph build

[mbed-ci]

Build : FAILURE

Build number : 2731
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/7662/

[cmonr]

I really hope this isn't what I think it is.

/morph build

[mbed-ci]

Build : FAILURE

Build number : 2732
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/7662/

[0xc0170]

One more, if still removes, we need to check assembly IAR

/morph build

[mbed-ci]

Build : FAILURE

Build number : 2740
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/7662/

[0xc0170]

@theotherjimmy can you review these failures? Is it related to the IAR update that we already marked as questionable (specifically this PR #7061)

[theotherjimmy]

@TTornblom Could you take a look at this failure. I'm afraid that @0xc0170 is correct: it looks related to adding configuration to assembly.

[0xc0170]

astyle travis - please check it , this line is shown there

[0xc0170]

Any examples how this works, what error codes we can try to test?

[TTornblom]

Any test case I can use to check this?

[BlackstoneEngineering]

@TTornblom , sure, use https://armmbed.github.io/mbedos-error/?error=0x81234567

[TTornblom]

What I meant was how can I provoke the IAR related failures.

[cmonr]

@TTornblom You should be able to use any failing case in this repo. The logs all contain the commands that were used to build them.

A random example: http://mbed-os.s3-eu-west-1.amazonaws.com/builds/7662/FAIL/K64F/IAR/0a8fe4f0d8c3da350bd5fda9bfee7bb29ef50a09_build_log_K64F_IAR.txt

For reference, you can actually checkout PR commits from a repo.
Something like the following should work:

git clone https://github.com/ARMmbed/mbed-os
cd mbed-os
git fetch origin refs/pull/7662/head:pr7662
git checkout pr7662

[0xc0170]

@TTornblom Any progress with reproducing the failure?

[TTornblom]

Sorry no.

We have been unable to reproduce this in house, and the version used (7.80) is no longer maintained so we can't, with reasonable effort, produce any debug binaries.

For the issues where iasmarm fails with error -11, which I assume is a segmentation fault, can a core dump be collected for analysis?

[cmonr]

@OPpuolitaival @ARMmbed/mbed-os-test Is ti possible to get a core dump of the problem?

[cmonr]

Going to try a rebuild to see if our current configuration dumps the segfault.

/morph build

[mbed-ci]

Build : FAILURE

Build number : 2872
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/7662/

[0xc0170]

I rebased, and compiled it with ARM, IAR and GCC ARM, seems to be working but functional test is still needed

[cmonr]

/morph build

[mbed-ci]

Build : SUCCESS

Build number : 2969
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/7662/

Triggering tests

/morph test
/morph export-build
/morph mbed2-build

[mbed-ci]

Exporter Build : SUCCESS

Build number : 2584
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/7662/

[mbed-ci]

Test : FAILURE

Build number : 2722
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/7662/2722

[cmonr]

/morph test

[mbed-ci]

Test : SUCCESS

Build number : 2727
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/7662/2727

[mattbrown015]

I believe the URL is generating a warning:

Compile [ 54.4%]: mbed_error.c
[Warning] mbed_error.c@392,23: unknown escape sequence: '/'

Could it be because I'm building on Windows (with GCC)?

Not the end of the world I know but I'd rather it didn't! :-)

[cmonr]

@mattbrown015 It's completely possible. Would you mind opening an issue so that we can track it?

[kegilbert]

@mattbrown015 thanks for pointing this out! I see the same warning in Linux using GCC_ARM.

@cmonr Do you need the // between 'https:/' and '/armmbed' in the below string?
"\"\\nFor more info, visit: https:/\\/armmbed.github.io/mbedos-error/?error=0x%08X\""
https://github.com/ARMmbed/mbed-os/blob/master/platform/mbed_lib.json#L75

The printing mechanics in the error handler are a bit different from printf due to the context, but the above string doesn't seem to actually be formatted correctly (you'd get an invalid URL from printf at least).