... | ... | @@ -65,11 +65,11 @@ This launch configuration can be started in the *Run and Debug* tab of VSCode. |
|
|
|
|
|
IntelliJ configuration example for running the jar in the **install** folder:
|
|
|
|
|
|
![Config1](img/config1.png "Select Edit configurations.")
|
|
|
![Config1](/img/config1.png "Select Edit configurations.")
|
|
|
|
|
|
![Config2](img/config2.png "Create a new JAR config.")
|
|
|
![Config2](/img/config2.png "Create a new JAR config.")
|
|
|
|
|
|
![Config3](img/config3.png "Select the jar and the working directory.")
|
|
|
![Config3](/img/config3.png "Select the jar and the working directory.")
|
|
|
|
|
|
|
|
|
### Debugging the hardware_emulator
|
... | ... | @@ -81,7 +81,7 @@ The steps to step through/set breakpoints in the hardware_emulator are a bit mor |
|
|
- Build the [hardware_emulator](https://git.rwth-aachen.de/monticore/EmbeddedMontiArc/simulators/hardware_emulator) in debug mode.
|
|
|
- Replace the `hardware_emulator_lib` file alongside the basic-simulator jar with the debug version.
|
|
|
- Start the basic-simulator.
|
|
|
- Attach to the Java thread of the simulator with a C++ debugger.
|
|
|
- Attach to the Java thread of the simulator with a C++ debugger (attach inside the hardware_emulator project).
|
|
|
- Set your breakpoints in the C++ project, run the simulator.
|
|
|
- To return to using the default release version of the hardware_emulator, just delete the library alongside the basic-simulator jar; it will be re-exported.
|
|
|
|
... | ... | |