Hmm... Thanks a lot. I think the problem may be related to the
connects/disconnects. Even if I am always reconnecting blocks, some freezes
happen sometimes in the disconnect() commands.
Is the patch you are refering to the new gnu version 3.5.3?
Also, I would like to know if there is a better me
On Fri, Apr 6, 2012 at 9:56 AM, ikjtel wrote:
>
>
> On Thu, Apr 5, 2012 at 5:11 AM, Tom Rondeau wrote:
>
>> You can use the following link as a guide to debugging segfaults when
>> they occur:
>>
>> http://gnuradio.org/redmine/projects/gnuradio/wiki/FAQ#How-do-I-debug-GNU-Radio-in-Python
>
> Hi To
On Thu, Apr 5, 2012 at 5:11 AM, Tom Rondeau wrote:
> You can use the following link as a guide to debugging segfaults when
> they occur:
>
> http://gnuradio.org/redmine/projects/gnuradio/wiki/FAQ#How-do-I-debug-GNU-Radio-in-Python
Hi Tom
I've noticed this issue pop up a few times on the list
On Thu, Apr 5, 2012 at 5:11 AM, frankist wrote:
>
> It seems I found the solution, in spite of not knowing the reason.
>
> I just have to re-assign a new block to each block variable every time I
> re-connect them. It seems that connecting and disconnecting the same blocks
> several times was the
It seems I found the solution, in spite of not knowing the reason.
I just have to re-assign a new block to each block variable every time I
re-connect them. It seems that connecting and disconnecting the same blocks
several times was the cause for the segmentation fault.
frankist wrote:
>
> Hi
Hi,
I am having a hard time with a "segmentation fault" error. I am no expert in
python (I just started to use it last week) but I find it difficult to
believe that a segmentation fault error would appear in python code.
However, I am not using any block made by me.
So this is the part of my cod
