Hello,
first let me say that I'm quite glad with Ozone, to have a working debugger on Linux.
When working with it on an existing project I get the screenshot as attached during debugging (ozone_normal.png).
When I reload the project and flash it into the target then I would expect to also see the same sources displayed, but the code is not displayed at all (ozone_reload.png).
I would expect to see the sources displayed even directly after loading the project. But after flashing the code into the target I would surely expect to see the code.
If I right-click into the code window then I get the normal context menu with "Set Breakpoint", "View Disassembly", ... which does not make sense without source code.
I'm not sure if this behavior is intended, I did not find anything in the documentation. From other debuggers I only know the behavior in a way that the sources are displayed when a project is saved and then loaded again. I think it would at least be a good improvement to Ozone.
I use 2.20j on Linux.
The directory structure (if this matters for reproducing the behavior) of the project is like this:
Thanks for any hints,
Torsten
first let me say that I'm quite glad with Ozone, to have a working debugger on Linux.
When working with it on an existing project I get the screenshot as attached during debugging (ozone_normal.png).
When I reload the project and flash it into the target then I would expect to also see the same sources displayed, but the code is not displayed at all (ozone_reload.png).
I would expect to see the sources displayed even directly after loading the project. But after flashing the code into the target I would surely expect to see the code.
If I right-click into the code window then I get the normal context menu with "Set Breakpoint", "View Disassembly", ... which does not make sense without source code.
I'm not sure if this behavior is intended, I did not find anything in the documentation. From other debuggers I only know the behavior in a way that the sources are displayed when a project is saved and then loaded again. I think it would at least be a good improvement to Ozone.
I use 2.20j on Linux.
The directory structure (if this matters for reproducing the behavior) of the project is like this:
Thanks for any hints,
Torsten