VS Arduino - ESP32-S3 throws exeception at start of debug

May 13^th, 2025 at 3:23pm (UTC)

Before logging an issue, please update to the latest release of Visual Micro from the Downloads Page.

When Logging a Support Issue in the Forum, please ensure you have also:-

Save the new Output to a Text File and....

Support requests without the output above may be impossible to answer, so please help us to help you

‹ Previous Topic | Next Topic ›

Pages: 1

ESP32-S3 throws exeception at start of debug (Read 1150 times)

Rod C Newbies Offline Posts: 5 Joined: Oct 8^th, 2023	ESP32-S3 throws exeception at start of debug Dec 20^th, 2023 at 5:29pm	Print Post
	As soon the debug session starts I get an exception - marked below. extern "C" void app_main() { #if ARDUINO_USB_CDC_ON_BOOT && !ARDUINO_USB_MODE Serial.begin(); #endif #if ARDUINO_USB_MSC_ON_BOOT && !ARDUINO_USB_MODE MSC_Update.begin(); #endif #if ARDUINO_USB_DFU_ON_BOOT && !ARDUINO_USB_MODE USB.enableDFU(); #endif #if ARDUINO_USB_ON_BOOT && !ARDUINO_USB_MODE USB.begin(); #endif loopTaskWDTEnabled = false; <----- THIS LINE THROWS EXCEPTION "Exception unhandled. Debugger was unable to continue the process" initArduino(); xTaskCreateUniversal(loopTask, "loopTask", getArduinoLoopTaskStackSize(), NULL, 1, &loopTaskHandle, ARDUINO_RUNNING_CORE); } I have had issues with this in the past but usually, 30% of the time it will run, now it fails 100% of the time

	Please Register or Login to the Forum to see File Attachments
	IP Logged

Simon@Visual Micro Administrator Offline Posts: 2697 Joined: Feb 13^th, 2019	Re: ESP32-S3 throws exeception at start of debug Reply #1 - Dec 20^th, 2023 at 5:39pm	Print Post
	Thanks for the report. Does changing the Optimization to "No Optimization" help in any way? (just as this is code from the ESP32 core itself) Can you attach a log after trying to begin the debug session, with the vMicro > Uploader > Verbose option enabled as well? (This will allow us to see the final debugging launch command in use, and potentially alter it to start debugging after this line has happened)


	WWW Facebook Twitter YouTube IP Logged

Rod C Newbies Offline Posts: 5 Joined: Oct 8^th, 2023	Re: ESP32-S3 throws exeception at start of debug Reply #2 - Dec 20^th, 2023 at 7:38pm	Print Post
	So that took me down a rabbit hole. Switching to "No Optimization" and then Cleaning. gave me this error "ld.exe: FS\\vfs_api.cpp.o:(.literal._ZN2fs8FileImplD5Ev[_ZN2fs8FileImplD5Ev]+0x0): undefined reference to vtable for fs::FileImpl" I switched back to "No Project optimization" but still got the error. I have had this in the past and the only way around it was to dump the project and re-import all the source and setup again. I did this, and the error went away and now the project debugger is also working again. I still have the optimization at "No Project Optimization" as I had some compilation issues. But now I have everything working I was reluctant to switch back to "No optimization" in case I had to repeat the exercise again, unless you think this will cause me issues down the road?


	IP Logged

Rod C Newbies Offline Posts: 5 Joined: Oct 8^th, 2023	Re: ESP32-S3 throws exeception at start of debug Reply #3 - Dec 20^th, 2023 at 8:17pm	Print Post
	I am still having issues, i have reinstalled everything. I am hopeful for some assistance, when everyone gets back after the holidays, all refreshed and ready to go! I have reconstructed everything, and the first error has gone away. Currently, whether, I attach to process or start a new debug session I get . "Unable to start debugging. Unexpected GDB output from command -exec-run. Don't know how to run. Try "help target" i have attached a new output.txt. So far i seem to have had poor results with debugging, I had no success with Mega2560, I switched to the ESP-32-S3 because of its internal USB-JTAG debugging options, and had some success with small sketches, but since loading my main project it fails 98% of the time. That said I love the ESP-32-S3 chip! Rod --------- Dev 20th Response ----- So I spoke to soon! I was able to attach to the process a couple of times, but building and starting the debugger has continued to have the same original error and now if i attach to the process it does the same thing. I have attached the micro-build log as previously requested, plus the debug tab log. thanks, Rod
	« Last Edit: Jan 1^st, 2024 at 1:23am by Rod C »
	Please Register or Login to the Forum to see File Attachments
	IP Logged

Pages: 1

‹ Previous Topic | Next Topic ›