Not only does objdump show that func_start_addr all 0s, but the func_start_addr in the kernel module's sframe table is also incorrect. I'll prepare a repro so we can investigate this. > > I can share a fix for 32589 so atleast we can verify that the starting > point is sane. > Great! Thanks. This will be helpful for comparing the values from the sframe table with the values we obtain at runtime