[Discuss-gnuradio] seg fault in volk_32f_s32f_multiply_32f_a_sse gnuradio v 3.6.1

2012-08-24 Thread ikjtel
At the moment it's easily reproducible.  Same app runs under GR v3.3 with no trouble. Let me know if I can provide any more info - in particular, perhaps there's a special GDB command to dump the "xmm" register set? Best Regards Max ~~

Re: [Discuss-gnuradio] A silly question

2012-08-24 Thread Josh Blum
On 08/24/2012 06:26 AM, sumitstop wrote: > > Thanks Ryan...it worked for the three UHD warnings. Now I shall do something > about > http://files.ettus.com/uhd_docs/manual/html/general.html#disabling-or-redirecting-prints-to-stdout Make this one-time call in c++ at the start of your process.

Re: [Discuss-gnuradio] get_gpio() help

2012-08-24 Thread Josh Blum
On 08/24/2012 09:00 AM, Frederick Lee wrote: > On Thu, Aug 23, 2012 at 5:54 PM, Samuel Ibarra wrote: > >> Hello, >> >> Thank you for your help Frederick. The problem that I am having is that I >> don't really understand how I can get the read_gpio() value into my python >> code. Once I get the

Re: [Discuss-gnuradio] LLLL error printout

2012-08-24 Thread Josh Blum
On 08/24/2012 09:12 AM, Anisha Gorur wrote: > Hello, > Very quick question, I'm trying to transmit a signal that I have created, > and in the console output at the beginning of the transmission, I get this > printout: LL. The error is not continuous, it stops after about 10 > L's. What do

[Discuss-gnuradio] LLLL error printout

2012-08-24 Thread Anisha Gorur
Hello, Very quick question, I'm trying to transmit a signal that I have created, and in the console output at the beginning of the transmission, I get this printout: LL. The error is not continuous, it stops after about 10 L's. What does this mean? Thanks, -Anisha __

Re: [Discuss-gnuradio] get_gpio() help

2012-08-24 Thread Frederick Lee
On Thu, Aug 23, 2012 at 5:54 PM, Samuel Ibarra wrote: > Hello, > > Thank you for your help Frederick. The problem that I am having is that I > don't really understand how I can get the read_gpio() value into my python > code. Once I get the value to my python code, then I will be able to create >

Re: [Discuss-gnuradio] A silly question

2012-08-24 Thread sumitstop
Thanks Ryan...it worked for the three UHD warnings. Now I shall do something about ~ linux; GNU C++ version 4.4.3; Boost_104000; UHD_003.004.003-177-g584b7ae2 -- Opening a USRP2/N-Series device... -- Current recv frame size: 1472 by

Re: [Discuss-gnuradio] Profiling GNU Radio flow graphs

2012-08-24 Thread Felix Wunsch
Hi, using oprofile is quite easy. Basically you configure your profiler, start it, start your application, kill it after some time, kill the profiler and look at the results. You don't have to set any special compiler flags. However, if you want to get annotated source, you need to compile wi

Re: [Discuss-gnuradio] A silly question

2012-08-24 Thread Ryan Wolfarth
If you execute the following commands you will get rid of those warnings. These adjust the maximum read and write buffer sizes allowed that the OS is allowed to use for network interfaces. See more here: http://wwwx.cs.unc.edu/~sparkst/howto/network_tuning.php sudo sysctl -w net.core.rmem_max=500

[Discuss-gnuradio] A silly question

2012-08-24 Thread sumitstop
Hi Community , Whenever we open a UHD device following message appears on the terminal : linux; GNU C++ version 4.4.3; Boost_104000; UHD_003.004.003-177-g584b7ae2 -- Opening a USRP2/N-Series device... -- Current recv frame size: 1472 bytes -- Curre

Re: [Discuss-gnuradio] Profiling GNU Radio flow graphs

2012-08-24 Thread Carles Fernandez
Hi Felix, we have some notes on code profiling here: http://gnss-sdr.org/documentation/how-profile-code We use the tools described there in a C++-only flowgraph, but I hope some of them will also work for you. Best regards, Carles On Fri, Aug 24, 2012 at 8:28 AM, Qing Yang wrote: > Hi Felix