[dedvalson]

Hi,

In response to your request, I reloaded my toolchain and it did in fact solve the problem.

Thanks for the help.

Don

[dedvalson]

Wow, I left out all the details.

This is an ESP-IDF 5.02 project.

I am using:

ESP32 toolchain 12.2.0/12.1/r1

VisualGDB 5.6R9 (build 4777)

 

[dedvalson]

Just tried the __cplusplus guard, it made no difference.

Thanks for the suggestion.

 

[dedvalson]

That was a good suggestions and pointed me in a different direction. If you look at the existing esp_log.h there are 4 places where there is a preprocessor statement as follows:

#if defined(__cplusplus) && (__cplusplus > 201703L)

I just changed them to:

#if defined(__cplusplus) && (__cplusplus > 201703L) && defined(USE_VA_ARGS)

This preserves the clang ability to make sure the arguments match the format statement.

Thanks,

Don

 

[dedvalson]

Hi,

The choice  “locate the toolchain manually”  does not appear to exist.

I have

• “Select a third party toolchain by locating gdb.exe,
• “Locate an IAR/Keil/CXSTM8 compiler installation”
• “Download more Toolchains…”

What am I missing?

[dedvalson]

Support Renewed.

[dedvalson]

Oh, on a somewhat related issue, I can’t find EPS32 tool chain 8.4.0/8.1.0/r1 in the VisualGDB Package manager. I have several projects using it that I don’t really want to update. Is it still available somewhere?

[dedvalson]

Hi,

I wanted to let you know that when I installed the most recent debug methods (20210125) the changes that I sent you above were only half included. The additions to the interfaces.xml were there but the additions to edp.xml were not. It wasn’t hard to add them back in but I thought you might want to fix that before the next release.

Thanks,

Don

 

[dedvalson]

Hi,

I have been using this regularly and it has save me so much effort. I really appreciate your input.

I wanted to ask if it might be possible to add one more minor feature in a future release. When I pull down the menu “Debug Using” dropdown on the Debug properties page I see 4 “Tumpa” entries since I have 4 boards. Underneath that it does give the USB address in small letters but those are hard to remember. If it would be possible to allow the user to rename these entries (or at least add a 1-4 at the end) that would be very helpful.

I know this is minor but it would be nice.

 

Don

 

[dedvalson]

Hi,

This worked just as you said it would. I still had the R3 toolchain and a less recent version of VisualGDB. But that made me wonder if I was doing something wrong with updates. I have “Check for updates automatically” selected in the VisualGDB package manager but I did not get any notice that either of these were available. Have they been available for long? Was I doing something wrong?

Thanks,

Don

 

[dedvalson]

Hi,

Thanks for the pointer, it worked perfectly.

I have attached the files.

This will save me a lot of time.

Don

Attachments:

You must be logged in to view attached files.

[dedvalson]

Hi,

Thanks for quick response. That did solve the problem.

I am sort of stuck with 4.1 because I need a feature from it. But I will be staying with 4.1 as it is today until it is officially released.

Thanks again,

 

Don

[dedvalson]

Thanks!

[dedvalson]

Hi,

I was able to track this down to a configuration problem after changing to CMake. Previously I had the number of breakpoints limited to 2 (which is how many hardware breakpoints the ESP-32 can support). I failed to transfer that setting and it appears that the VisualGDB code was inserting more than 2 breakpoints even if I only  had one user specified breakpoint.  Flash breakpoints are not currently supported on the ESP-32. Putting that limitation back in solved the problem. The ESP-IDF code still shouldn’t crash under these circumstances but that does seem to be the issue.

 

Thanks,

Don

 

[dedvalson]

Never mind, I answered my own question. Yes, that works well. I can put them all in a solution file and choose which projects to build that way.

Thanks for the suggestion.

 

Don

 

[Author]

Posts