Re: [Discuss-gnuradio] Debug Issue

[Tom Rondeau]

2011/8/2 fangming he <address@hidden>:
> Hi, All,
>
> I added mutiple printf or cout in many *.cc or *.h files when I debug my
> demo. However, it did not print it on the screen, because those files are
> overwrite when I make the GNU Radio again. I check it, those files are
> automatically generated when I make GNU Radio.
>
> Currently, I just copy those file that I inserted printf/cout to some other
> directory and changing the class and files name. Then I test it.
> I know it is not a smart way.  But I have no better solution.
>
> Any one has any suggestion on debuging this issue? Changing code generator?
>
> I do hope to get your guys's good solution and give me a example.
>
> Best,
>
> Fangming


Which files are you trying to debug? There are many blocks that are
autogenerated, and you'll see the source files as
gr_something_XX.cc.t, gr_something_XX.h.t, and gr_something_XX.i.t.
These are the template files, and these blocks are usually found in
the gengen directory. A python script is run during the build process
that builds all of the versions of the code, like for
short-in/short-out, float-in/float-out, etc.

If you want to debug these files, look for those template (.t) files
and edit them.

Tom