# Running benchmark\_rx.py in debugging mode

**URL:** <https://www.ruby-forum.com/t/running-benchmark-rx-py-in-debugging-mode/183890>\
**Category:** GNU Radio\
**Created:** [February 22, 2010, 11:03am UTC](https://www.ruby-forum.com/t/running-benchmark-rx-py-in-debugging-mode/183890 "2010-02-22T11:03:11Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![alapati\_iitm](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/e56c9b/32.png) [@alapati\_iitm](https://www.ruby-forum.com/u/alapati_iitm)\
**Post date:** [February 22, 2010, 11:03am UTC](https://www.ruby-forum.com/t/running-benchmark-rx-py-in-debugging-mode/183890/1 "2010-02-22T11:03:11Z")

</div>

hi everyone,  
Is there any way for me to run the benchmark\_tx and  
benchmark\_rx.py files in debugging mode so that I can see the entire  
flow  
structure? I am curious to know the steps that take place from the  
calling  
of the python script to the point where the modulated symbols are  
transmitted via the USB2.0.  
Regards,  
Amarnath

---

<div class="post-metadata">

**Author:** ![alapati\_iitm](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/e56c9b/32.png) [@alapati\_iitm](https://www.ruby-forum.com/u/alapati_iitm)\
**Post date:** [February 22, 2010, 2:39pm UTC](https://www.ruby-forum.com/t/running-benchmark-rx-py-in-debugging-mode/183890/2 "2010-02-22T14:39:45Z")

</div>

On Mon, Feb 22, 2010 at 3:55 AM, amarnath alapati  
[removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> hi everyone,  
> Is there any way for me to run the benchmark\_tx and  
> benchmark\_rx.py files in debugging mode so that I can see the entire flow  
> structure? I am curious to know the steps that take place from the calling  
> of the python script to the point where the modulated symbols are  
> transmitted via the USB2.0.  
> Regards,  
> Amarnath

I’m not sure exactly what you mean by ‘debugging mode’. You can  
attach a running flowgraph to gdb  
([GNU Radio - Free & Open Source Software Radio](http://www.gnu.org/software/gnuradio/doc/howto-write-a-block.html#debugging)),  
but I would think that that’s lower level stuff than you are looking  
for, and the multi-threaded scheduler makes it difficult to monitor  
specific flows for a less-than-expert gdb user.

At the current point in time there doesn’t seem to be a way to ‘single  
step’ through a flow graph and monitor the inputs and outputs, no  
‘gnuradio debugger’ as it were. I think this would be a nice feature  
to have, both in grc and as command line tool, but I think it’s a  
pretty hard thing to implement given the current code.

You can turn on logging the benchmark\_\*x files which will give you the  
modulation steps only, if that is what you are interested in. You  
will have to view the log files with octave or matlab and synchronize  
them yourself.

Jason

---

<div class="post-metadata">

**Author:** ![alapati\_iitm](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/e56c9b/32.png) [@alapati\_iitm](https://www.ruby-forum.com/u/alapati_iitm)\
**Post date:** [February 22, 2010, 7:37pm UTC](https://www.ruby-forum.com/t/running-benchmark-rx-py-in-debugging-mode/183890/3 "2010-02-22T19:37:42Z")

</div>

On Mon, Feb 22, 2010 at 07:34:01AM -0600, Jason U. wrote:

> On Mon, Feb 22, 2010 at 3:55 AM, amarnath alapati  
> [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:
> 
> > hi everyone,  
> > Is there any way for me to run the benchmark\_tx and  
> > benchmark\_rx.py files in debugging mode so that I can see the entire flow  
> > structure? I am curious to know the steps that take place from the calling  
> > of the python script to the point where the modulated symbols are  
> > transmitted via the USB2.0.  
> > Regards,  
> > Amarnath

You can turn logging on.

Try

$ benchmark\_rx.py --help

You’ll have to look at the code to understand what’s in each log file.

Eric