Using MapViewer with STM32F7

[invertium]

Hi govind!

Awesome tool you wrote here :)

I'm trying to investigate the memory used on my STM32F7 but I'm running into the following error:

The paths all seem fine, no spaces or weird characters.

Any idea what can be done to make the tool work? Thanks!

Regards Julian

[govind-mukundan]

Could be some wierd path within the map file itself, would be useful if you could attach it too

On Wed, 10 Feb 2021, 01:16 Juledev, notifications@github.com wrote:

Hi govind!

Awesome tool you wrote here :)

I'm trying to investigate the memory used on my STM32F7 but I'm running into the following error:

[image: image] https://user-images.githubusercontent.com/15930333/107400425-174d9880-6b02-11eb-92a0-b1e08f811592.png

The paths all seem fine, no spaces or weird characters.

[image: image] https://user-images.githubusercontent.com/15930333/107400557-32b8a380-6b02-11eb-8ecd-da996b8bf795.png

Any idea what can be done to make the tool work? Thanks!

Regards Julian

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/govind-mukundan/MapViewer/issues/10, or unsubscribe https://github.com/notifications/unsubscribe-auth/AATBK3YARAESVPHB77JZ56DS6FUVVANCNFSM4XLMFP6A .

[invertium]

I realized I was compiling under WSL and then running MapViewer under windows, however compiling with Windows didn't help either. I'm afraid I can't share that particular map file for security reasons, I'll see if I can find a sanitized version with the same issue.

As a suggestion: Might it make sense to wrap a try catch block around that and output the offending path in the error message?

[govind-mukundan]

Yes that's a good suggestion. I'll look into that.

Alternatively, If you run the map viewer project under visual studio you should be able to find the offending line easily.

On Wed, 10 Feb 2021, 16:12 Juledev, notifications@github.com wrote:

I realized I was compiling under WSL and then running MapViewer under windows, however compiling with Windows didn't help either. I'm afraid I can't share that particular map file for security reasons, I'll see if I can find a sanitized version with the same issue.

As a suggestion: Might it make sense to wrap a try catch block around that and output the offending path in the error message?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/govind-mukundan/MapViewer/issues/10#issuecomment-776525156, or unsubscribe https://github.com/notifications/unsubscribe-auth/AATBK33TYKHMGYIQDW4ISMTS6I5VZANCNFSM4XLMFP6A .

[DaPa]

Encountered this error too with a TI MSP430 binary.

With a workaround as in https://github.com/DaPa/MapViewer/commit/b5d97ff6db62f45a387b08d179a6399ff9096e09 a dialog shows the problematic path, but the app continues fine after that...