I can try re-building the OOT module. I don't think I know how to '....with logging same-same as GR's'. I have two questions: 1) How do I know how GR was built? With logging? 2) Assuming I know the answer to 1) above, where do I change things so that OOT compiles with with same setting for logging?
Vipin On Sun, Jul 16, 2017 at 5:24 PM, Michael Dickens <[email protected]> wrote: > Maybe you're hitting the logger_ptr bug? See < > https://github.com/gnuradio/gnuradio/issues/1383 > <https://github.com/gnuradio/gnuradio/issues/1383#issuecomment-315605543> > > for more info. It happens when GR is built with logging enabled but not > log4cpp, and then the OOT is built either with logging enable and log4cpp > or logging not enabled. The "free" on gr::block ends up corrupting the > stack because the logger_ptr is of the wrong size in the OOT block (when > compared with that compiled into gnuradio_runtime). Not sure if this is the > issue here, but this is happening during gr::flowgraph::clear (which just > clears the blocks and then edges), so, maybe? An easy test is to rebuild > the OOT with logging same-same as GR's. - MLD > > On Sun, Jul 16, 2017, at 03:29 PM, Vipin Sharma wrote: > > Here is the system config: > > vipin@pp001:~/a1/gr-howto/build$ uname -a > Linux pp001 4.8.0-58-generic #63~16.04.1-Ubuntu SMP Mon Jun 26 18:08:51 > UTC 2017 x86_64 x86_64 x86_64 GNU/Linux > > >
_______________________________________________ Discuss-gnuradio mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
