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
 
Page Index Toggle Pages: 1 Send TopicPrint
Normal Topic Unable to start debugging. Unexpected GDB output from command "-exec-run". Don't know how to run. (Read 2628 times)
JFR
Newbies
*
Offline


Posts: 7
Joined: Jan 4th, 2023
Unable to start debugging. Unexpected GDB output from command "-exec-run". Don't know how to run.
Jan 4th, 2023 at 3:44pm
Print Post  
Windows 10
Visual Studio 2022
Visual Micro - Release 22.11.28.15
Arduino 1.6/1.8
ATmega2560
avr_debugger (latest) installed from https://github.com/jdolinay/avr_debug

Using 'standard' Blink sketch.

When selecting Debug:Serial, everything works fine.
When selecting Debug:Hardware with GDB Stub, I get the error message in the Subject

======================
/*
Blink without Delay

Turns onand off a light emitting diode(LED) connected to a digital pin,
without using the delay() function.This means that other code can run at the
same time without being interrupted by the LED code.

The circuit :
-Use the onboard LED.
- Note : Most Arduinos have an on - board LED you can control.On the UNO, MEGA
and ZERO it is attached to digital pin 13, on MKR1000 on pin 6. LED_BUILTIN
is set to the correct LED pin independent of which board is used.
If you want to know what pin the on - board LED is connected to on your
Arduino model, check the Technical Specs of your board at :
https://www.arduino.cc/en/Main/Products

created 2005
by David A.Mellis
modified 8 Feb 2010
by Paul Stoffregen
modified 11 Nov 2013
by Scott Fitzgerald
modified 9 Jan 2017
by Arturo Guadalupi

This example code is in the public domain.

http://www.arduino.cc/en/Tutorial/BlinkWithoutDelay
*/

// constants won't change. Used here to set a pin number:
#ifdef VM_DEBUG_GDB
#include <app_api.h>
#include <avr_debugger.h>
#include "avr8-stub.h"
#endif
const int ledPin = LED_BUILTIN;// the number of the LED pin

// Variables will change:
int ledState = LOW;             // ledState used to set the LED

// Generally, you should use "unsigned long" for variables that hold time
// The value will quickly become too large for an int to store
unsigned long previousMillis = 0;        // will store last time LED was updated

// constants won't change:
const long interval = 1000;           // interval at which to blink (milliseconds)

void setup() {
#ifdef VM_DEBUG_GDB
    debug_init();
#endif
    // set the digital pin as output:
    pinMode(ledPin, OUTPUT);
}

void loop() {
#ifdef VM_DEBUG_GDB
    breakpoint();
#endif
    // here is where you'd put code that needs to be running all the time.

    // check to see if it's time to blink the LED; that is, if the difference
    // between the current time and last time you blinked the LED is bigger than
    // the interval at which you want to blink the LED.
    unsigned long currentMillis = millis();

    if (currentMillis - previousMillis >= interval) {
        // save the last time you blinked the LED
        previousMillis = currentMillis;

        // if the LED is off turn it on and vice-versa:
        if (ledState == LOW) {
            ledState = HIGH;
        }
        else {
            ledState = LOW;
        }

        // set the LED with the ledState of the variable:
        digitalWrite(ledPin, ledState);
    }
}
« Last Edit: Jan 4th, 2023 at 4:21pm by JFR »  

Please Register or Login to the Forum to see File Attachments
Back to top
 
IP Logged
 
Tim@Visual Micro
Administrator
*****
Offline


Posts: 12137
Location: United Kingdom
Joined: Apr 10th, 2010
Re: Unable to start debugging. Unexpected GDB output from command "-exec-run". Don't know how to run.
Reply #1 - Jan 4th, 2023 at 11:09pm
Print Post  
Please add this to the top of the code or remove the use of #if VM_DEBUG_GDB and the associated #endif

#define VM_DEBUG_GDB

The define is not being added correctly in the current release, we will resolve that over the coming days


  
Back to top
IP Logged
 
JFR
Newbies
*
Offline


Posts: 7
Joined: Jan 4th, 2023
Re: Unable to start debugging. Unexpected GDB output from command "-exec-run". Don't know how to run.
Reply #2 - Jan 5th, 2023 at 3:27pm
Print Post  
Hi Tim

Thank you for the reply!  I have tried both with the #define, and without and it still gives the same error.

Any additional insight is appreciated.
  

Please Register or Login to the Forum to see File Attachments
Back to top
 
IP Logged
 
JFR
Newbies
*
Offline


Posts: 7
Joined: Jan 4th, 2023
Re: Unable to start debugging. Unexpected GDB output from command "-exec-run". Don't know how to run.
Reply #3 - Jan 5th, 2023 at 3:30pm
Print Post  
... without #ifdef
  

Please Register or Login to the Forum to see File Attachments
Back to top
 
IP Logged
 
JFR
Newbies
*
Offline


Posts: 7
Joined: Jan 4th, 2023
Re: Unable to start debugging. Unexpected GDB output from command "-exec-run". Don't know how to run.
Reply #4 - Jan 5th, 2023 at 3:31pm
Print Post  
Micro Build results without #ifdef attached
  

Please Register or Login to the Forum to see File Attachments
Back to top
 
IP Logged
 
Simon@Visual Micro
Administrator
*****
Offline


Posts: 2370
Joined: Feb 13th, 2019
Re: Unable to start debugging. Unexpected GDB output from command "-exec-run". Don't know how to run.
Reply #5 - Jan 5th, 2023 at 3:59pm
Print Post  
Thanks for the detail and the logs.

Can you update to the latest version which is available from our Downloads Page (below), which should resolve the issue (the launch.json where the COM Port has too many slashes in it):
https://www.visualmicro.com/page/Arduino-Visual-Studio-Downloads.aspx
  
Back to top
 
IP Logged
 
JFR
Newbies
*
Offline


Posts: 7
Joined: Jan 4th, 2023
Re: Unable to start debugging. Unexpected GDB output from command "-exec-run". Don't know how to run.
Reply #6 - Jan 5th, 2023 at 5:04pm
Print Post  
THANK YOU!!!
  
Back to top
 
IP Logged
 
Simon@Visual Micro
Administrator
*****
Offline


Posts: 2370
Joined: Feb 13th, 2019
Re: Unable to start debugging. Unexpected GDB output from command "-exec-run". Don't know how to run.
Reply #7 - Apr 13th, 2023 at 8:36am
Print Post  
Off-Topic replies have been moved to this Topic.
  
Back to top
 
IP Logged
 
Page Index Toggle Pages: 1
Send TopicPrint