Hi and thank you for a great tool!
Ozone v3.20e
Ubuntu 20.04
With gdb I can choose to show disassembly in a source centric (disassemble /m FUNCTION) or machine code centric (disassemble /s FUNCTION) view.
It looks to me like Ozone provides a similar distinction through the Source Viewer and Disassembly Window.
But I'm a little puzzed about what algorithm the Source Viewer uses when displaying disassembly.
The main function in my attached program has a bunch of inlined functions when building with -Os.
For usart_setup Ozone displays the inlined function body. But for clock_setup and gpio_setup it don't.
Is this the expected behavior? At first I thought you were just not associating inlined code with the original source lines, but that does happen for usart_setup.
In contrast: gdb shows assembly code associated for both clock_setup and gpio_setup.
Attaching a small libopencm3 project for stm32f4discovery (I've deleted the libopencm3 folder due to the forum software not allowing uploads larger than 1M.
But the elf file is there and the c-file with the main function. If you want to download libopencm3 and rebuild the project, just type make.
Attaching a screenshot of Ozones source viewer and the output of gdb /m main
Ozone v3.20e
Ubuntu 20.04
With gdb I can choose to show disassembly in a source centric (disassemble /m FUNCTION) or machine code centric (disassemble /s FUNCTION) view.
It looks to me like Ozone provides a similar distinction through the Source Viewer and Disassembly Window.
But I'm a little puzzed about what algorithm the Source Viewer uses when displaying disassembly.
The main function in my attached program has a bunch of inlined functions when building with -Os.
For usart_setup Ozone displays the inlined function body. But for clock_setup and gpio_setup it don't.
Is this the expected behavior? At first I thought you were just not associating inlined code with the original source lines, but that does happen for usart_setup.
In contrast: gdb shows assembly code associated for both clock_setup and gpio_setup.
Attaching a small libopencm3 project for stm32f4discovery (I've deleted the libopencm3 folder due to the forum software not allowing uploads larger than 1M.
But the elf file is there and the c-file with the main function. If you want to download libopencm3 and rebuild the project, just type make.
Attaching a screenshot of Ozones source viewer and the output of gdb /m main