OK, have tracked it down thanks to help from the list.
> Christophe Seguinot writes:
>> deleting all contents of ./build, then going through cmake, make, make
install, and ldconfig.
> did you sudo make uninstall before removing the build folder (if not they
may be some remaining libgnuradio 3.8
Hi Tom
Can you check that /usr/lib/x86_64-linux-gnu only contains
libgnuradio 3.8.2 (and no 3.8.1 nor 3.8.0) libraires using ll
/usr/lib/x86_64-linux-gnu/libgnuradio* ?
I have been in such a trouble which breaks gnuradio-companion
(Ubuntu 20.04)
Hi Marcus - thanks for the reply. Previously I had rebuilt my OOT by
deleting all contents of ./build, then going through cmake, make, make
install, and ldconfig.
cmake reported:
-- Found PythonInterp: /usr/bin/python3 (found version "3.8.2")
-- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpyt
Hi Tom,
just to verify: You did recompile your module against 3.8.2.0 and not
accidentally linked it against a gnuradio-something.so of 3.8.1.0 that
lingered on your system? I ask because these things really happen often.
Best regards,
Marcus
On 06/09/2020 23.48, Tom McDermott wrote:
My Ubu
A few notes:
1) The automatic update may be bad. The GNU Radio PPA has other
procedural problems and this may be another.
2) Your OOT may be over-writing some Python code. I've seen this before.
The different error behavior depends on exactly where your code got
loaded in memory.
3) Believ
My Ubuntu 20.04 updated automatically to 3.8.2.
SInce the update I have been getting memory error messages in the
gnuradio-companion terminal window.
These errors did not occur in 3.8.1. The error is not consistent, always
get one of the following three error messages:
double free or corruption
