Dear List,
Im finding it particularly challenging to debug new gnu radio blocks. If
I have a printf() in my work() function, the output is not written to
std out; is it redirected elsewhere? What other methods are you using
for debugging gnu radio blocks?
Sincerely,
Tommy James Tracy II
Ph.D Student
High Performance Low Power Lab
University of Virginia
Phone: 913-775-2241
On Tue, Oct 29, 2013 at 02:20:47AM -0400, Tommy T. II wrote:
I’m finding it particularly challenging to debug new gnu radio blocks. If I
have a printf() in my work() function, the output is not written to std out; is
it redirected elsewhere? What other methods are you using for debugging gnu
radio blocks?
Tommy,
you might need to flush the output to directly see stuff.
If you use std::cout and std::endl, that happens automatically.
Also, are you debugging through unit tests? Are you doing ctest -V?
We have this tutorial:
http://gnuradio.org/redmine/projects/gnuradio/wiki/TutorialsDebugging
…but I admit it could be a bit longer. Perhaps you can add to this
page once you’ve figured out your problem?
Thanks,
MB
–
Karlsruhe Institute of Technology (KIT)
Communications Engineering Lab (CEL)
Dipl.-Ing. Martin B.
Research Associate
Kaiserstraße 12
Building 05.01
76131 Karlsruhe
Phone: +49 721 608-43790
Fax: +49 721 608-46071
www.cel.kit.edu
KIT – University of the State of Baden-Württemberg and
National Laboratory of the Helmholtz Association
On Tue, Oct 29, 2013 at 5:15 AM, Martin B. (CEL)
[email protected] wrote:
Also, are you debugging through unit tests? Are you doing ctest -V?
We have this tutorial:
http://gnuradio.org/redmine/projects/gnuradio/wiki/TutorialsDebugging
…but I admit it could be a bit longer. Perhaps you can add to this
page once you’ve figured out your problem?
Thanks,
MB
Also, check out the new logging infrastructure:
http://gnuradio.org/doc/doxygen/page_logger.html
Tom