Jun 6th, 2025 at 9:12pm (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:-

  • Enabled vMicro > Compiler > Show Build Properties
  • Re-Compile your program with these settings enabled
  		Save the new Output to a Text File and....
  • Click the Reply button and attach as .txt file OR
  • Click here to Email us with the file attached, and a link to your post
Support requests without the output above may be impossible to answer, so please help us to help you
 
  VS Arduino › Visual Micro › Hardware Debugging (GDB, GDB WiFi, GDB Stub) › ESP32-S3: Unable to start debugging. Unexpected GDB output from command "-exec-run".
‹ Previous Topic | Next Topic ›
Page Index Toggle Pages: [1]  Send TopicPrint
Very Hot Topic (More than 25 Replies) ESP32-S3: Unable to start debugging. Unexpected GDB output from command "-exec-run". (Read 11945 times)
discman
Junior Member
**
Offline


Posts: 27
Joined: Apr 13th, 2023
ESP32-S3: Unable to start debugging. Unexpected GDB output from command "-exec-run".
Apr 13th, 2023 at 5:58am
Print Post  
I am getting this same error message "Unexpected GDB output….. -exec -run" when trying to “Attach to Process…”.

Previously. I'd been successfully debugging ESP32 with an ESP-PROG.  Just now, I’ve changed to an ESP32 S3.  Using the D+, D- lines, and have the USB JTAG/Serial debug COM port showing up okay.  Everything (Uploader, board.txt, port etc.) are set up per your video.  Both VisualStudio and vMicro (2023.220.2205) were updated as of few days ago.

BTW, USB JATG/serial debug unit (Interface 0) is showing up in Device Mgr, but I set up driver for (Interface 2) in Zadig per your video.  Is that right?

Build and upload to S3 okay, just cannot Attach to Process.  Please help!

Thank you.
« Last Edit: Apr 13th, 2023 at 8:36am by Simon@Visual Micro »  
Back to top
 
IP Logged
 
Simon@Visual Micro
Administrator
*****
Offline


Posts: 2710
Joined: Feb 13th, 2019
Re: ESP32-S3: Unable to start debugging. Unexpected GDB output from command "-exec-run".
Reply #1 - Apr 13th, 2023 at 8:44am
Print Post  
Thanks for the report.

I believe interface 2 is correct for the driver installation, it should show as the "USB JTAG/serial debug unit" on the correct interface.

Please enable the below options:
  • vMicro > Compiler > Verbose
  • vMicro > Compiler > Show Build Properties
  • vMicro > Uploader > Verbose


Then run the build and upload to the board, and try the Debug > Attach to Process.

If you can attach the complete output as a text file from the Output Window > Micro Build it will help us to understand the issue in more detail.

If there is any output in the Output Window > Debug please also attach this as well as a text file.
  
Back to top
WWWFacebookTwitterYouTube  
IP Logged
 
discman
Junior Member
**
Offline


Posts: 27
Joined: Apr 13th, 2023
Re: ESP32-S3: Unable to start debugging. Unexpected GDB output from command "-exec-run".
Reply #2 - Apr 13th, 2023 at 3:55pm
Print Post  
Thank you for your reply.  A real silly question: Just how do I attach text files?  (I'm new to this forum)  None of the menu icons seems to be for attaching local file.
  
Back to top
 
IP Logged
 
Simon@Visual Micro
Administrator
*****
Offline


Posts: 2710
Joined: Feb 13th, 2019
Re: ESP32-S3: Unable to start debugging. Unexpected GDB output from command "-exec-run".
Reply #3 - Apr 13th, 2023 at 5:27pm
Print Post  
You should see an Attachments section below the Message box where you reply/post, which has a file chooser available to select files on disk.
  
Back to top
WWWFacebookTwitterYouTube  
IP Logged
 
discman
Junior Member
**
Offline


Posts: 27
Joined: Apr 13th, 2023
Re: ESP32-S3: Unable to start debugging. Unexpected GDB output from command "-exec-run".
Reply #4 - Apr 13th, 2023 at 7:11pm
Print Post  
I attached a combined Build, Upload and Debug log file.
Thanks in advance.
  
Please Register or Login to the Forum to see File Attachments
Back to top
 
IP Logged
 
Simon@Visual Micro
Administrator
*****
Offline


Posts: 2710
Joined: Feb 13th, 2019
Re: ESP32-S3: Unable to start debugging. Unexpected GDB output from command "-exec-run".
Reply #5 - Apr 14th, 2023 at 11:20am
Print Post  
Thanks for the log.

Can you try amending your local board.txt entry to the one in the attached file?

Simply applying the configuration we sent over should automatically download the package from our website and unpack it, when you try to attach the debugger.

If it does not, you can download our copy of OpenOCD from:
https://visualmicro.com/downloads/tools/openocd-esp32-0.10.1-2021.11.11/openocd-...

Then unzip it to "C:\ProgramData\vMicro\tools" and it should then work with the override we provided and no further modifications.
  
Please Register or Login to the Forum to see File Attachments
Back to top
WWWFacebookTwitterYouTube  
IP Logged
 
discman
Junior Member
**
Offline


Posts: 27
Joined: Apr 13th, 2023
Re: ESP32-S3: Unable to start debugging. Unexpected GDB output from command "-exec-run".
Reply #6 - Apr 14th, 2023 at 3:56pm
Print Post  
Thanks for the response.  Unfortunately, Attach to Process still fails with the modification.  Attached is a debug log file combined with my connection/settings.
Thanks.
  
Please Register or Login to the Forum to see File Attachments
Back to top
 
IP Logged
 
discman
Junior Member
**
Offline


Posts: 27
Joined: Apr 13th, 2023
Re: ESP32-S3: Unable to start debugging. Unexpected GDB output from command "-exec-run".
Reply #7 - Apr 24th, 2023 at 4:41am
Print Post  
Simon,

I am still stuck at the same state when trying to “Attach to Process…”.  The output shown in above screenshot are still valid.
Can you please see if you have any suggestion?  I can’t use the S3 with VisualMicro without getting through this.

Thanks.
  
Back to top
 
IP Logged
 
Simon@Visual Micro
Administrator
*****
Offline


Posts: 2710
Joined: Feb 13th, 2019
Re: ESP32-S3: Unable to start debugging. Unexpected GDB output from command "-exec-run".
Reply #8 - Apr 24th, 2023 at 11:40am
Print Post  
Could you try installing the Espressif Driver for the USB-JTAG device via Device Manager to see if this improves the situation?
https://dl.espressif.com/dl/idf-driver/idf-driver-esp32-usb-jtag-2021-07-15.zip
  
Back to top
WWWFacebookTwitterYouTube  
IP Logged
 
discman
Junior Member
**
Offline


Posts: 27
Joined: Apr 13th, 2023
Re: ESP32-S3: Unable to start debugging. Unexpected GDB output from command "-exec-run".
Reply #9 - Apr 25th, 2023 at 1:40am
Print Post  
Thank you for the reply.

Form the Device Manager, I right-click on the USB/JATG unit (Interface 0) (COM11) port, Then “Update Driver”, “Browse my computer”.   The dialog then indicates “The best driver already installed”.

I then tried “Let me pick from list of available drivers”.  The “Have Disk”, browse to the folder and “OK”.  But here is the message: 
“The folder you specified doesn’t contain a compatible software driver for your device.  If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems.”

So it does not let me install anything.  Any other way to install this driver?
  
Back to top
 
IP Logged
 
Simon@Visual Micro
Administrator
*****
Offline


Posts: 2710
Joined: Feb 13th, 2019
Re: ESP32-S3: Unable to start debugging. Unexpected GDB output from command "-exec-run".
Reply #10 - Apr 25th, 2023 at 10:12am
Print Post  
Before updating the driver can you change the board.txt entry for the debug path to the one in the attached text file, and add in the extra one? 

This will use the OpenOCD tools that Espressif package with the board package, and lower the speed at which the debugger tries to communicate at.

The driver can be installed via Powershell as shown on the below page, however the above changes may resolve the issue without the need for this:
https://docs.espressif.com/projects/esp-idf/en/latest/esp32s3/api-guides/jtag-de...
  
Please Register or Login to the Forum to see File Attachments
Back to top
WWWFacebookTwitterYouTube  
IP Logged
 
discman
Junior Member
**
Offline


Posts: 27
Joined: Apr 13th, 2023
Re: ESP32-S3: Unable to start debugging. Unexpected GDB output from command "-exec-run".
Reply #11 - Apr 25th, 2023 at 11:00pm
Print Post  
Simon,
Thanks for your help again, unfortunately, the same error remains unresolved.  I first changed the board.txt to the following:

debug.toolingsystem=gdbscript
# Use Builtin ESP32S3 OpenOCD Tools instead of vMicro Clones
tools.openocd.debug.path={runtime.tools.openocd-esp32.path}
tools.esps3usb.vmserver.args={params.verbose} -l "{{build.path}/{build.project_name}_DebugOpenOCD.log}" -s "{path}/share/openocd/scripts/" -f "{path}/share/openocd/scripts/interface/{build.openocddebugger}" -c "adapter speed 5000" -c "set ESP32_RTOS none" {initCmd} 
# Ensure the board resets when using Debug > Attach to Process for convenience
vs-cmd.Debug.AttachtoProcess.tools.openocd.initCmd=-c "init; reset halt"


That did not help.  Then I force installed the driver: 
PS C:\Users\Joe\Downloads\idf-driver-esp32-usb-jtag-2021-07-15> Invoke-WebRequest 'https://dl.espressif.com/dl/idf-env/idf-env.exe' -OutFile .\idf-env.exe; .\idf-env.exe driver install --espressif
Downloading https://dl.espressif.com/dl/idf-driver/idf-driver-esp32-usb-jtag-2021-07-15.zip to idf-driver-esp32-usb-jtag-2021-07-15.zip
* extracted: md64/install-filter.exe" (44544 bytes)
* extracted: md64/libusb0.dll" (76384 bytes)
* extracted: md64/libusb0.sys" (52832 bytes)
* extracted: md64/libusb0_x86.dll" (46592 bytes)
* extracted: md64/libusbK.dll" (99128 bytes)
* extracted: md64/libusbK.sys" (47928 bytes)
* extracted: md64/libusbK_x86.dll" (84280 bytes)
* extracted: md64/WdfCoInstaller01011.dll" (1795952 bytes)
* extracted: md64/winusbcoinstaller2.dll" (1002728 bytes)
* extracted: SB_JTAG_debug_unit.cat" (9738 bytes)
* extracted: SB_JTAG_debug_unit.inf" (4642 bytes)
* extracted: 86/install-filter.exe" (46592 bytes)
* extracted: 86/libusb0.dll" (46592 bytes)
* extracted: 86/libusb0.sys" (42592 bytes)
* extracted: 86/libusb0_x86.dll" (67680 bytes)
* extracted: 86/libusbK.dll" (84280 bytes)
* extracted: 86/libusbK.sys" (42552 bytes)
* extracted: 86/WdfCoInstaller01011.dll" (1629040 bytes)
* extracted: 86/winusbcoinstaller2.dll" (851176 bytes)
Requesting elevation of privileges for: C:\Users\Joe\Downloads\idf-driver-esp32-usb-jtag-2021-07-15\idf-env.exe driver install --espressif --no-download
Exit code: 0x2a
PS C:\Users\Joe\Downloads\idf-driver-esp32-usb-jtag-2021-07-15>

Any other idea?
  
Back to top
 
IP Logged
 
discman
Junior Member
**
Offline


Posts: 27
Joined: Apr 13th, 2023
Re: ESP32-S3: Unable to start debugging. Unexpected GDB output from command "-exec-run".
Reply #12 - Jun 26th, 2023 at 9:19pm
Print Post  
After updating to 2023_0507_2203, I tried to see if it could help this previously unresolved problem.  Unfortunately, it did not.

I went through the sequence in the above thread again and the same error persisted.

I’d really want to be able to use Visual Micro hardware debugging for the ESP32-S3.  Can you please help?
Thank you.
« Last Edit: Jun 26th, 2023 at 10:30pm by Tim@Visual Micro »  
Please Register or Login to the Forum to see File Attachments
Back to top
 
IP Logged
 
Simon@Visual Micro
Administrator
*****
Offline


Posts: 2710
Joined: Feb 13th, 2019
Re: ESP32-S3: Unable to start debugging. Unexpected GDB output from command "-exec-run".
Reply #13 - Jun 30th, 2023 at 8:33am
Print Post  
Thanks for the update and detail.

We have been able to sucessfully get the debugging running on our ESP32-S3 board, with one important wiring change (GPIO3 -> GND).

By default I believe the fuse bits are set on the chip to prefer USB Debugging, and pulling GPIO3 low will allow JTAG debugging via the JTAG pins.

If you run the ESPFuse.exe as shown in the "Check Fuse Bits" section of the below page, and attach the output we will be able to tell you if this is required:
https://www.visualmicro.com/page/ESP32S3-JTAG-Debugging.aspx
  
Back to top
WWWFacebookTwitterYouTube  
IP Logged
 
discman
Junior Member
**
Offline


Posts: 27
Joined: Apr 13th, 2023
Re: ESP32-S3: Unable to start debugging. Unexpected GDB output from command "-exec-run".
Reply #14 - Jun 30th, 2023 at 11:18pm
Print Post  
Hi Simon,
Thanks for your reply. 
I followed the instruction and burned the STRAP efuse.  Here’s the result:
  STRAP_JTAG_SEL (BLOCK0)          Enable selection between usb_to_jtagor pad_to_jtag = True R/W (0b1)  through GPIO3
  DIS_USB_JTAG (BLOCK0)               Disable usb_serial_jtag-to-jtag function   = False R/W (0b0)

However, I now have a more immediate problem Embarrassed.  I’ve inadvertently set the driver for Interface 1 of ESP-PROG to the following (attached).  Now, I cannot reset the driver to recognize Interface 0 again. 

How can I get the required Interface 0 back?
Thanks very much.
« Last Edit: Jul 2nd, 2023 at 6:08pm by discman »  
Please Register or Login to the Forum to see File Attachments
Back to top
 
IP Logged
 
Simon@Visual Micro
Administrator
*****
Offline


Posts: 2710
Joined: Feb 13th, 2019
Re: ESP32-S3: Unable to start debugging. Unexpected GDB output from command "-exec-run".
Reply #15 - Jul 3rd, 2023 at 9:02am
Print Post  
Thanks for the update and detail.

The driver looks correct for Interface 0 from your images (WinUSB) for using Hardware Debugging.

Interface 1 is the Serial Port passthrough so should end up back on the FTDI Bus Driver.  If you right click the device in Device Manager, and then select Properties > Driver Tab > Rollback Driver, this should restore the previous driver before Zadig was used.
  
Back to top
WWWFacebookTwitterYouTube  
IP Logged
 
Kabron
Full Member
***
Offline


Posts: 170
Joined: Nov 1st, 2015
Re: ESP32-S3: Unable to start debugging. Unexpected GDB output from command "-exec-run".
Reply #16 - Aug 2nd, 2023 at 3:10pm
Print Post  
I have exactly the same error output.
I tryed all above tricks with no luck.
BUT debugging works with platformio and VisualGDB,
so my hardware setup is correct.
Board LILYGO T-Display-S3
« Last Edit: Aug 2nd, 2023 at 3:12pm by Kabron »  
Back to top
 
IP Logged
 
Simon@Visual Micro
Administrator
*****
Offline


Posts: 2710
Joined: Feb 13th, 2019
Re: ESP32-S3: Unable to start debugging. Unexpected GDB output from command "-exec-run".
Reply #17 - Aug 10th, 2023 at 2:10pm
Print Post  
We have amended the instructions for using the ESP32S3 with USB Debugging on our page below:
https://www.visualmicro.com/page/ESP32S3-USB-Debugging.aspx

The board.txt entries have changed, and you may also need to pull GPIO3 high before powering the board up to ensure the USB-JTAG debugging is available.

If you continue to have issues with the ESP32S3 USB Debugging please attach the updated logs.
  
Back to top
WWWFacebookTwitterYouTube  
IP Logged
 
discman
Junior Member
**
Offline


Posts: 27
Joined: Apr 13th, 2023
Re: ESP32-S3: Unable to start debugging. Unexpected GDB output from command "-exec-run".
Reply #18 - Aug 15th, 2023 at 12:11am
Print Post  
Simon,
Thanks for the update.  However, I have a Catch-22.  My subscription expired the week before, and I don’t want to renew it without being able to use JTAG debugging.  Perhaps I’m asking for too much, but is there a way to provide me a 5-day trial.  So I may verify your new instruction before I’ll renew my subscription.  Without S3 JTAG debugging, unfortunately, I’d have no use for vMicro. Undecided
Thanks very much.
« Last Edit: Aug 15th, 2023 at 12:12am by discman »  
Back to top
 
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12191
Location: United Kingdom
Joined: Apr 10th, 2010
Re: ESP32-S3: Unable to start debugging. Unexpected GDB output from command "-exec-run".
Reply #19 - Aug 15th, 2023 at 1:01am
Print Post  
You can use your existing license key to re-activate. We have added 10 days from today.
« Last Edit: Aug 15th, 2023 at 1:09am by Tim@Visual Micro »  
Back to top
WWWFacebookTwitterYouTube  
IP Logged
 
discman
Junior Member
**
Offline


Posts: 27
Joined: Apr 13th, 2023
Re: ESP32-S3: Unable to start debugging. Unexpected GDB output from command "-exec-run".
Reply #20 - Aug 15th, 2023 at 6:14am
Print Post  
Thanks very much for the extension.  Using the suggested board.txt I was able to test the S3 operation and gotten further than before.  With a stripped-down LED blinker test sketch, I was able to upload (flash), break at breakpoint, and examine variables!

But when I clicked either the “Break All” or the “Stop Debugging” button while the sketch is running, Visual Studio immediately became completely non-responsive to any key or mouse input.  No further output appeared in the Output window.  Could not close Visual Studio.  The only way out was via “End task” from Windows’ Task Manager.

Attached is the Output windows prior to me clicking “Break All”.  Then everything froze, no further output.
Please see if you can pick up any clue to overcome the hang.  Thanks again.
  
Please Register or Login to the Forum to see File Attachments
Back to top
 
IP Logged
 
discman
Junior Member
**
Offline


Posts: 27
Joined: Apr 13th, 2023
Re: ESP32-S3: Unable to start debugging. Unexpected GDB output from command "-exec-run".
Reply #21 - Aug 15th, 2023 at 6:30pm
Print Post  
And when I attempted to run my regular-size ESP32-S3 app, it could not get far.  It appears that as the sketch started execution, it always broke (exception) at main_app(), as shown in the attached logs.
  
Please Register or Login to the Forum to see File Attachments
Back to top
 
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12191
Location: United Kingdom
Joined: Apr 10th, 2010
Re: ESP32-S3: Unable to start debugging. Unexpected GDB output from command "-exec-run".
Reply #22 - Aug 15th, 2023 at 6:48pm
Print Post  
We need the info requested in yellow above. 

This type of error can be related to optimisation settings. Each microconroller tends to have slightly different requirements. The requested output will allow us to see your config.
  
Back to top
WWWFacebookTwitterYouTube  
IP Logged
 
discman
Junior Member
**
Offline


Posts: 27
Joined: Apr 13th, 2023
Re: ESP32-S3: Unable to start debugging. Unexpected GDB output from command "-exec-run".
Reply #23 - Aug 15th, 2023 at 7:08pm
Print Post  
Tim,
You’re correct.  I have not followed the requirement of building with “No Optimization”.  It’s because the build would failed unless I build with “No Project Optimization”.  It appears to be related to my app is including/using the LittleFS library?  The error message is attached.  So I must get passed this linker error first.
  ld.exe: FS\\vfs_api.cpp.o:(.literal._ZN2fs8FileImplD5Ev[_ZN2fs8FileImplD5Ev]+0x0): undefined reference to vtable for fs::FileImpl
If you have any idea on how to resolve the linker error, please let me know. 
Thank you much.
  
Please Register or Login to the Forum to see File Attachments
Back to top
 
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12191
Location: United Kingdom
Joined: Apr 10th, 2010
Re: ESP32-S3: Unable to start debugging. Unexpected GDB output from command "-exec-run".
Reply #24 - Aug 15th, 2023 at 7:30pm
Print Post  
Thanks for the info. 

This relates to how to use you microcontroller and is not related specifically to Visual Micro. One suggestion might be avoid debug of code that fails, set breakpoints in areas that can be debugged. 

Alternatively there are #pragma statements that the esp32 code supports. They to control optimization for specific chunks of code. Something like the following. You can either disable or enable opimization. This code diables but you might think about editing the littleFS lib and forcing optimization to that used by a Release build.


#pragma GCC push_options
#pragma GCC optimize ("O0")

int non_optimized_function() {
    // This function is compiled without optimizations.
    int x = 5;
    for (int i = 0; i < 10; ++i) {
        x += i;
    }
    return x;
}

#pragma GCC pop_options


-- NOTE --

pragma can also be used in conjuntion with the #defines visual micro provides when compiling for debug. That will allow #pragma settings to be ignored when building in release mode.
« Last Edit: Aug 15th, 2023 at 7:32pm by Tim@Visual Micro »  
Back to top
WWWFacebookTwitterYouTube  
IP Logged
 
discman
Junior Member
**
Offline


Posts: 27
Joined: Apr 13th, 2023
Re: ESP32-S3: Unable to start debugging. Unexpected GDB output from command "-exec-run".
Reply #25 - Aug 16th, 2023 at 6:11am
Print Post  
After seeing another thread mentioning the same linker error, I tried backing the esp32 Board Mgr from 2.0.9 to 2.0.5.  The code is able to build under “No optimization”.  So now, we can return get back to the hang problem a day earlier before getting diverted.  To recap:

Thanks very much for the extension.  Using the suggested board.txt I was able to test the S3 operation and gotten further than before.  With a stripped-down LED blinker test sketch, I was able to upload (flash), break at breakpoint, and examine variables!

But when I clicked either the “Break All” or the “Stop Debugging” button while the sketch is running, Visual Studio immediately became completely non-responsive to any key or mouse input.  No further output appeared in the Output window.  Could not close Visual Studio.  The only way out was via “End task” from Windows’ Task Manager.

Attached is the Output windows prior to me clicking “Break All”.  Then everything froze, no further output.
Please see if you can pick up any clue to overcome the hang.  Thanks again.
  
Please Register or Login to the Forum to see File Attachments
Back to top
 
IP Logged
 
Kabron
Full Member
***
Offline


Posts: 170
Joined: Nov 1st, 2015
Re: ESP32-S3: Unable to start debugging. Unexpected GDB output from command "-exec-run".
Reply #26 - Aug 16th, 2023 at 7:09am
Print Post  
Got some success in USB JTAG internal debug.
Test setup: VS2017/19 VM 2023_0507_1914.
Board: LILYGO T-Display-S3 
ESP32 pack 2.0.9. New board.txt.
Test programm:
Code
Select All
long t1;
void setup()
{
	pinMode(LCD_BL, OUTPUT);
	Serial.begin(115200);
}

void loop()
{
	t1 = millis();
	digitalWrite(LCD_BL, HIGH);
	Serial.println(digitalRead(LCD_BL));
	delay(100);
	digitalWrite(LCD_BL, LOW);
	Serial.println(digitalRead(LCD_BL));
	delay(100);
	Serial.println(millis() - t1);
}


1. First strange thing. Regardless Release/Debug mode after downloading/reset, code works as expected about 4s. I.e. LED blinks at 5 Hz 4S, then changed to 2Hz. If serial terminal connected it blinks 5Hz endlessly while connected. 
2. Attach to process works only if any breakpoints are set. Working controls: "Continue", "StepIn/Out/Over", "Stop". (see AttachLog.txt)
3. Attaching to process without breakpoints starts, but no breakpoints are available.("The breakpoint will not currently be hit"). Any manipulation with debug controls("Pause/Stop") lead to irreversible hangup of VS.
See Attach_No_BP.txt.
« Last Edit: Aug 16th, 2023 at 7:12am by Kabron »  
Please Register or Login to the Forum to see File Attachments
Back to top
 
IP Logged
 
Kabron
Full Member
***
Offline


Posts: 170
Joined: Nov 1st, 2015
Re: ESP32-S3: Unable to start debugging. Unexpected GDB output from command "-exec-run".
Reply #27 - Aug 16th, 2023 at 7:10am
Print Post  
It's a little surprising:
# Ensure the Flash Size is set to 0 to prevent issues

Are there any other settings to test?
« Last Edit: Aug 16th, 2023 at 7:15am by Kabron »  
Please Register or Login to the Forum to see File Attachments
Back to top
 
IP Logged
 
discman
Junior Member
**
Offline


Posts: 27
Joined: Apr 13th, 2023
Re: ESP32-S3: Unable to start debugging. Unexpected GDB output from command "-exec-run".
Reply #28 - Aug 17th, 2023 at 7:14pm
Print Post  
I share your pain, Kabron.  You’ve described my exact predicament.  After weeks of struggles, I can finally connect the debugger to the S3 and execute code.  But, as you’ve said… 1) Fail to set breakpoint after “Attaching”, 2) Pause and Stop controls cause complete hang in Visual Studio.  It’s like working with one hand tied behind my back. Sad

It seems to be some “communication issue” between the GDB, VS, vMicro?

Can vMicro investigate the above two problems please?
  
Back to top
 
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12191
Location: United Kingdom
Joined: Apr 10th, 2010
Re: ESP32-S3: Unable to start debugging. Unexpected GDB output from command "-exec-run".
Reply #29 - Aug 17th, 2023 at 7:42pm
Print Post  
Thanks for the info. We are looking into it. Unfortunately, Visual Micro doesn't play a part in it. We provide the json settings/script to VS and ask it to launch. We might have to raise it with Microsoft but will continue to experiment.
  
Back to top
WWWFacebookTwitterYouTube  
IP Logged
 
Simon@Visual Micro
Administrator
*****
Offline


Posts: 2710
Joined: Feb 13th, 2019
Re: ESP32-S3: Unable to start debugging. Unexpected GDB output from command "-exec-run".
Reply #30 - Oct 19th, 2023 at 3:01pm
Print Post  
Can you install the latest version (23.1006.01) from the top of the board below, and then try debugging again?
https://www.visualmicro.com/forums/YaBB.pl?board=VS_ARDUINO_EXT_RELEASES

This should resolve the issues where the break all / stop / add breakpoint when the target is running.
  
Back to top
WWWFacebookTwitterYouTube  
IP Logged
 
discman
Junior Member
**
Offline


Posts: 27
Joined: Apr 13th, 2023
Re: ESP32-S3: Unable to start debugging. Unexpected GDB output from command "-exec-run".
Reply #31 - Oct 30th, 2023 at 5:38am
Print Post  
Simon,
Thank you for following up.  I’d love to test the solution, however, my subscription has since expired.
If you could grant me a 5-day license to try it out, I’ll report the result.
     Joe
  
Back to top
 
IP Logged
 
discman
Junior Member
**
Offline


Posts: 27
Joined: Apr 13th, 2023
Re: ESP32-S3: Unable to start debugging. Unexpected GDB output from command "-exec-run".
Reply #32 - Nov 1st, 2023 at 1:13am
Print Post  
Simon,

The start/stop/breakpoint are now working smoothly!  Thanks very much for fixing it (23.1006.02).

There’s one other thing that your team may want to investigate: In order to build the S3 code with No Optimization, I have to use ESP32 “Board Manager” ver 2.0.5.  Building with newer versions will result in link failure.  This was communicated earlier in this same thread.  I know vMicro may not be in control with this link error.  But as Espressif updates keep coming (now at 2.0.14), having to remain with 2.0.5 will eventually become a problem.
  
Back to top
 
IP Logged
 
Simon@Visual Micro
Administrator
*****
Offline


Posts: 2710
Joined: Feb 13th, 2019
Re: ESP32-S3: Unable to start debugging. Unexpected GDB output from command "-exec-run".
Reply #33 - Nov 1st, 2023 at 9:19am
Print Post  
Thanks for the update and confirming the fix is working as expected.

The Optimization issue should be avoidable by using the "No Project + Libraries" option which will still allow the ESP32 core code to be optimised.  This issue would be something the Arduino ESP32 core team need to investigate if they feel it is relevant.
  
Back to top
WWWFacebookTwitterYouTube  
IP Logged
 
discman
Junior Member
**
Offline


Posts: 27
Joined: Apr 13th, 2023
Re: ESP32-S3: Unable to start debugging. Unexpected GDB output from command "-exec-run".
Reply #34 - Nov 4th, 2023 at 12:30am
Print Post  
That’s not what I am experiencing.  Using ESP32 board version 2.0.14 (most current), under “No Project + Libraries Opt”, the build failed:

ld.exe: FS\\vfs_api.cpp.o:(.literal._ZN2fs8FileImplD5Ev[_ZN2fs8FileImplD5Ev]+0x0): undefined reference to vtable for fs::FileImpl

Error linking for board ESP32S3 Dev Module (esp32_esp32s3)

While it’s something that the Arduino ESP core team needs to resolve, it’d be good for vMicro to notify them of this.

Thanks.
  
Back to top
 
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12191
Location: United Kingdom
Joined: Apr 10th, 2010
Re: ESP32-S3: Unable to start debugging. Unexpected GDB output from command "-exec-run".
Reply #35 - Nov 4th, 2023 at 1:00am
Print Post  
It's possible a library you are using does not support no optimization. What happens if you set project only?
  
Back to top
WWWFacebookTwitterYouTube  
IP Logged
 
discman
Junior Member
**
Offline


Posts: 27
Joined: Apr 13th, 2023
Re: ESP32-S3: Unable to start debugging. Unexpected GDB output from command "-exec-run".
Reply #36 - Nov 4th, 2023 at 1:36am
Print Post  
Tim,
Thanks for pointing that out.  I switched to “No Project opt” and it built okay.  The Breakpoint and Single-Stepping also appear to function fine.
  
Back to top
 
IP Logged
 
Page Index Toggle Pages: [1] 
Send TopicPrint
‹ Previous Topic | Next Topic ›
 
  « Board Index ‹ Board Top  

VS Arduino » Powered by YaBB 2.6.12!
YaBB Forum Software © 2000-2025. All Rights Reserved.