Actually you can “freeze” execution and spying every thread with gdb, or
just let sereval of them continue as your wish . Use data breakpoint can
trap the exact point where abnormal happens.
在 2019年1月12日星期六，Martin Braun 写道：
> Keep in mind, with the multi-threaded scheduler you wouldn't end up in
Keep in mind, with the multi-threaded scheduler you wouldn't end up in a
deterministic state. Unless of course you only want to debug the state of
your own block -- then you can do what WarMonkey suggested.
-- M
On Mon, Jan 7, 2019 at 11:43 AM Rudolf Wigblurr
wrote:
> Hi,
>
> Is it possible to
Yes you can debug any gnuradio c++ module with gdb.
Step 1 uninstall gnuradio.
Step 2 git clone gnuradio from github.
Step 3 build gnuradio with debug symbols on. ( cmake ..
-DCMAKE_BUILD_TYPE=Debug )
Step 4 reinstall custom build gnuradio.
Step 5 debug your application with gdb ( use qtcreator, vs
Hi Rudolf - That's a very cool idea, but to the best of my knowledge GNU
Radio can't do stepping like you describe. I think it would be an -excellent-
feature to add; not sure how one would deal with the non-deterministic
nature of threads waking / sleeping / executing when using the thread-per-
bl
Hi,
Is it possible to single step a flow graph?
I have a recorded stream of FSK modulated data with about 25 bursts of messages.
When this is later decoded I do not get 100% detection, about 4 of 25 bursts fails.
Now my thinking is can I play this burst by burst and see what is wrong.
S
