That indeed is the nuclear option. If you want to scale it back to
"daisy cutter" you can remove the src directory and inventory.dat...
and capture the debug output when the build breaks.
On Thu, Nov 12, 2015 at 8:02 AM, Simon Kennedy wrote:
> A couple of days ago I ran ./pybombs update and it fa
You can run pybombs with extra verbose flags (I usually recommend "-v
-v -v") to see what it's doing, but as part of the update process
it'll clean the source directories.
There's also "./pybombs inv" to see what pybombs thinks is installed.
I tend to wipe my target directory and just start fresh
On 11/24/2015 04:54 PM, Saulo Queiroz wrote:
Hi,
I got the following message after some (random) period of time running
a grc example (derived from gr-ieee802-11) on B210.
gr uhd usrp source0 - USRP Source Block caught rx error code: 2
In my grc I have one Sink and one Source UHD block. Bo
Hi,
I got the following message after some (random) period of time running a
grc example (derived from gr-ieee802-11) on B210.
gr uhd usrp source0 - USRP Source Block caught rx error code: 2
In my grc I have one Sink and one Source UHD block. Both has 2 active
channels configured as below:
mas
I think I've come across a bug with the pfb_clock_sync blocks set_taps
implementation. If I change a parameter in python that causes a change to
the filter tap variable being fed to the pfb_clock_sync block, which then
requires pfb_clock_sync.set_taps() to be called, the program will error out
with
On 24.11.2015 16:55, Tom Rondeau wrote:
> Marcus is usually quite to point out this link. Surprised he hasn't so
> far :p
You're right, I'm constantly surprising myself, too :P
Also, in your case, Ekko, I would also have pointed you to the more
specifically GDB-oriented tutorial,
http://gnuradio.
Hi Ekko,
really, use GDB, not Pdb. Just "run" your program, than "backtrace";
stepping through it is really really tedious, and isn't really extremely
helpful unless you know intimately where to look.
As Tom mentioned, the debugging (and the GDB) tutorial will be helpful.
Best regards,
Marcus
O
On Tue, Nov 24, 2015 at 10:47 AM, West, Nathan
wrote:
> We're short on information to actually determine what's wrong here. It
> looks like you're still using pdb, but I see different output/problem areas
> from your screenshots. The first one looks like it crashed in tb.start,
> and the second
We're short on information to actually determine what's wrong here. It
looks like you're still using pdb, but I see different output/problem areas
from your screenshots. The first one looks like it crashed in tb.start,
and the second one looks like it crashed just creating the channel model
block.
hi marcus
i use the gdb as you said,the i debug the python file again
run the fie step by step
i found that the there is some problem with ‘channel model’,just like
you can see that
self.channels_channel_model_0 = channels.channel_model(
function is init the channel model block
and the noise_vol
Hi Martin,
I think you got it right to insert the tag at least if you have a packet_len
tag (and maybe MIMO). There might be a performance issue, because we get buffer
underruns above 2 MHz sampling frequency, while not getting anyone with
continuous streaming.
Otherwise, any solution leading
11 matches
Mail list logo
