Hi all,
at the moment i try to debug an AVR microcontroller via Nemiver.
Unfortunately it doesn't work as expected. It seems that Nemiver
doesn't break the program at main(). Nevertheless i can halt the
program, set a breakpoint and continue it again. All breakpoints that i
introduced in this way are triggered correctly and intercepted by
Nemiver.
Of course, if i start a pure avr-gdb terminal debugging session that
starts with
(gdb) target remote localhost:6432
(gdb) break main
(gdb) c
everything works just fine.
The explained issue occurs if i start Nemiver by invoking:
nemiver --remote=localhost:6432 --gdb-binary=/usr/bin/avr-gdb
--log-debugger-output
~/Bildung/Electronics/Microcontroller/avr/atxmegaXXeXX/demo-buttons-01/main.elf
The debugging output is attached.
At this point i don't know whether i should file a bug report or i have
to adjust any setting?
I would be very happy if any more experienced Nemiver user comments my
usecase or give me a hint how i can achieve that the program breaks
upon reaching main().
With best regards
JohannesAttachment:
nemiver.stdout
Description: Binary data