Debugger breaks at wrong source line

[szabiaura]

Hi,

My debugging session on a ESP32-Ethernet-Kit is showing something very strange: when a breakpoint is hit, the debugger is actually on another line. Check this out:

Code: [Select all] [Expand/Collapse]

1. Thread 17 hit Breakpoint 3, protobuf_c_message_unpack (desc=0x3f407248 <device_info.descriptor>, allocator=0x3ffb133c <protobuf_c.allocator>, len=<optimized out>, data=<optimized out>) at /Users/cc/esp/esp-idf/components/protobuf-c/protobuf-c/protobuf-c/protobuf-c.c:3181
2. 3181            scanned_member_slabs[which_slab][in_slab_index++] = tmp;
3. info breakpoints
4. Num     Type           Disp Enb Address    What
5. 3       breakpoint     keep y   0x400e92b2 in protobuf_c_message_unpack at /Users/cc/esp/esp-idf/components/protobuf-c/protobuf-c/protobuf-c/protobuf-c.c:3179
6.     breakpoint already hit 1 time

GeSHi © Codebox Plus Extension

When the breakpoint is hit, it's on line 3184 whereas the info command returns line 3179 which is where I set my breakpoint in eclipse.

The source code is freshly built and flashed after idf.py fullclean. ESP-IDF version 4.1. Any idea what's happening?

Thanks, Szabi