Bloom icon indicating copy to clipboard operation
Bloom copied to clipboard

Issues when stepping into a static library

Open sven-hoek opened this issue 1 year ago • 7 comments

Not sure if stepping into the static library is the issue but it seems to happen whenever I try to step into or break in a statically-linked library function.

  • Bloom version: 1.0.0 (.deb, installed on Ubuntu 22.04)
  • Both library and firmware were built with -Og.
  • Debugging an ATmega328PB via DebugWire through an Atmel-ICE
  • Error message when trying to step into the function:
    [ERROR] Failed to decode AVR8 opcode at byte address 0x000001be - the instruction will have to be intercepted. Please enable debug logging, reproduce this message and report as an issue via https://bloom.oscillate.io/report-issue
    
  • Error message from avr-gdb:
    Breakpoint 1, main () at .././main.c:82
    82	    CH9120Initialisation();  // initialize the CH9120 Serial to Ethernet controller
    ../../src/gdb/gdbtypes.c:931: internal-error: type* create_range_type(type*, type*, const dynamic_prop*, const dynamic_prop*, LONGEST): Assertion `TYPE_LENGTH (index_type) > 0' failed.
    A problem internal to GDB has been detected,
    further debugging may prove unreliable.
    

When debugging within VSCode, the Debugging stops but when I run avr-gdb in the terminal and connect to Bloom's gdb-server, I can continue, though never able to step into a library function. Bloom itself doesn't always crash and so far I couldn't really pin down when it does. It happens when I am a few lines above a library function call and then try to step over (but not even the library function call itself)...I'll also report the bug on the avr-gdb side.

If there's anything else I could try or any info I could provide, let me know.

sven-hoek avatar Jul 21 '24 10:07 sven-hoek