[pavel_dlp]

Thx for your help! When i work with cpu with large memory – gcc is wery nice and debug work good. Thx for good Visual DBG! Work debug with small memory by different dbg is not a problem now.

Thx for replay!

Best regards, Pavel

[pavel_dlp]

Maybe it’s a kind of bug in ARM(Keil) compiler but the debug info produced by it is completely normal for “Ozone” J-Link debugger and there’s no problen with source code line numbers and symbols. Using GCC is very problematic because it produces much bigger code and has problems with some Mbed-OS runtime code parts. So I NEED to setup VisualGDB to work correctly when debugging code produced by ARM(Keil) compiler toolchain. I think you are also interested in illustration that VisualGDB is compatible with ARM compiler toolchain and Mbed-OS. I only need to know what additional informaition you require to solve the problem jointly.

Thanks a lot for your help.

[pavel_dlp]

Dear Support,

The reason you’ve pointed out doesn’t seem to be the real one. I’ve removed all the breakpoints and set just the single one in the main function. No breakpoints from other project but nothing changed, the error is the same. I added the log for you to analyse once more.

Thanks for you concern!

—
Pavel

Attachments:

You must be logged in to view attached files.

[pavel_dlp]

Thank you for replay! I checked build – all is ok. I will attached log file. Help me, please…

Attachments:

You must be logged in to view attached files.

[Author]

Posts