Closed KB4MDD closed 1 year ago
I've only looked at this for a minute, but f=0x152
seems suspicious to me. Any time of low address like that is almost always some kind of offset from NULL, e.g. f->member
when f is NULL. This would fit if member is 152 bytes into the struct, for instance. Further up though, the frame is definitely not NULL... one tactic that might help here is adding assertions liberally starting from the first stack frame and working up from there, asserting the frame is not NULL (since it seems like it might be). That could narrow down where things are going wrong. Not sure how I'd reproduce this since it looks like you're using hardware, but if you need guidance on where to add those in, let me know (but basically each stack frame function call is what I do).
Possible issue with fr not being initialized to zero at line 522. I will test as soon as I can get to the equipment.
In attempts to get chan_usrp up and operational, I encountered a core dump as it started to channel data.