Yes, you can use the Eclipse debugger if you incorporate some test apps into your project (you can always pull them out to release/publish).
The way I got it all pulled together is that I add new test executables (just C++ mains) to the project and manually added them to the cmake files in the <project>/lib directory. Then I set the debugger to run whichever test executable I wanted. Inside there I could instantiate my new classes and call whatever functions I want (such as work() or a modified work() just for testing purposes). For test data I would either use a real signal saved with a file sink in GNURadio and just read it in, or create a function in my test program to generate it. Then I could step through my modules with the debugger. I'm personally a big fan of debuggers. Trying to debug with print statements to me is too painful/slow from a development process perspective. On Sat, Oct 14, 2017 at 8:32 AM, Walter Grossman <[email protected]> wrote: > Were you able to use the debugger? If so, how? > > On Fri, Oct 13, 2017 at 5:14 PM, Michael Piscopo <[email protected]> > wrote: > >> I've had great success with Eclipse. I use it for all my OOT modules. >> >> On Fri, Oct 13, 2017 at 5:03 PM, Walter Grossman <[email protected]> >> wrote: >> >>> Does anyone have experience e using an idea integrated with gnu radio >>> for making c, c++ modules? Any recommendations? Eclipse? NetBeans? Don't do >>> it? >>> >>> _______________________________________________ >>> Discuss-gnuradio mailing list >>> [email protected] >>> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio >>> >>> >> >
_______________________________________________ Discuss-gnuradio mailing list [email protected] https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
