I'll do my best, but it might take me quite some time to get gdb set up
with the symbols you mentioned. C++/debugging doesn't come naturally for
me.
What it smells like to me is memory is being freed but then written to.
Then when the system goes to allocate memory it says hey that memory isn't
Hi Brad,
Sorry that I missed your mail for so long!
So, I'm pretty certain I've fixed a potential race condition when
accessing the data vector in vector sink lately:
https://github.com/gnuradio/gnuradio/pull/1445
But that should be included in the 3.7.11.1 release you're using... hm.
We
Ah, by the way, the function names where that error occurs are mangled
C++ names; I'll try to show what is what (using `c++filt` to demangle
the names)
> /lib64/libc.so.6(+0x7dd4d)[0x7fa14f448d4d]
> /lib64/libc.so.6(__libc_malloc+0x4c)[0x7fa14f44afbc]
OK, that's malloc; are we certain that this
The Vector Sink is coming in very handy for some experimentation I'm doing.
I'm analyzing the output of an FFT block which terminates into a float
vector sink. every few seconds from a thread which then calls reset() to
clear the contents in preparation for another read. This seems problematic
as
