Discover the new mydSPACE services: License Management, the new dSPACE Help, and dSPACE Chatbot for User Documentation. Find more information and support on our dedicated support page. Learn more & get support

FAQ 566: Debugging Virtual Artifacts with Eclipse IDE

Question

How do I attach the debugger to a simulation running in VEOS using Eclipse IDE?

Solution

Debugging the source code during SIL simulation is useful. It allows you to set breakpoints, inspect variables, and step through the code. The V-ECU workflow allows you to integrate ECU code into a simulated artifact, allowing errors to be identified early in development. During the integration process, it is often advantageous to use a debugger to investigate faults and errors in more detail. VEOS allows external debuggers to be attached to VPUs that are built with the Debug configuration.

To debug source code in a SIL simulation using Eclipse IDE:

  1. Load the offline simulation application (OSA) to VEOS.
  1. Get the unique Process ID from the Properties window of VEOS or via the Task Manager.
  1. Start Eclipse IDE.
  2. In the Eclipse window, create a new C/C++ project.
     
  1. In the Classic C Project dialog, enter the name of the debug project, select the compiler, and click Finish.
  1. Right-click on the debug project you created and select New-> Folder.
  1. In the New Folder dialog, select the current debug project and provide the path of the VEOS Build folder (containing source files, binaries and *.dll generated). Click “Finish”.
  1. In the Eclipse window, select Open Perspective, then select Debug from the dialog that opens.
  1. In the Eclipse window, click Debug and select Debug Configurations.
  1. In the Debug Configurations window, right-click on C/C++ Attach to Application and select “New Configuration”.
  1. In the new debug configuration that was created, give a name to the configuration in the “Main” tab. In the C/C++ Application field, enter the path of the *.dll file that was generated during the VEOS build. In the Build Configuration, select “Debug” and select the “Disable auto build” option.
  1. In the “Debugger Options” pane, define the path of the compiler.
  1. In the “Add Source” dialog, add a new compilation directory. Then, provide the path to the folder containing the source files and binaries in the VEOS build folder.
  1. Set up an example breakpoint. Once the VEOS simulation is loaded, check the Process ID.
  1. In the Eclipse window, set the breakpoint at the required lines in the code and click “Debug Configuration”. Select the debug project and click “Debug”.
  1. A new window opens. Search for the Process ID as seen in VEOS and click OK.
  1. In the Debug window, click the “Resume” icon.
  1. Navigate to VEOS and start the simulation. Once the debugger is connected, “Call Trace” will be visible and the simulation is paused until the debugger resumes execution[JP..

Verwandte Themen

  • FAQ 557
    FAQ 557

    How do I attach the debugger to a running VEOS simulation?

Tags

Date 2026-10-16
Produkt VEOS
Informationstyp FAQ (Häufig gestellte Fragen)
dSPACE Release 2026-A
Keywords SIL Support Central

Immer auf dem neuesten Stand mit unserem Newsletter-Service.

Mit unserem Newsletter-Service informieren wir Sie über aktuelle Anwendungsbeispiele, neue Lösungen und Produkte sowie über Schulungen und Veranstaltungen. Hier geht's zur Anmeldung.

Formularaufruf freigeben

An dieser Stelle ist ein Eingabeformular von Click Dimensions eingebunden. Dieses ermöglicht es uns Ihr Newsletter-Abonnement zu verarbeiten. Aktuell ist das Formular ausgeblendet aufgrund Ihrer Privatsphäre-Einstellung für unsere Website.

Externes Eingabeformular

Mit dem Aktivieren des Eingabeformulars erklären Sie sich damit einverstanden, dass personenbezogene Daten an Click Dimensions innerhalb der EU, in den USA, Kanada oder Australien übermittelt werden. Mehr dazu in unserer Datenschutzbestimmung.