Re: [Discuss-gnuradio] TX/RX with USRPN200 and GNURadio

Ok!! I have Ubuntu 12.04 in this PC http://www.amazon.com/HP-FF825AV-Workstation-2-8GHz-nVidia/dp/B00B90WIGE (Quad Core and 12GB RAM). With the scheme with loop I have: Generating: "/home/caruiz_ext/Escritorio/generadoresGNU/top_block.py" Generating: "/home/caruiz_ext/Escritorio/generadoresGNU

Re: [Discuss-gnuradio] segfault in volk_32f_x2_dot_prod_32f_a_generic

Hi Sergey, the segfault happens in a Volk kernel, which is an optimized numeric algorithm for a length of uniform data. The fact that the base pointer is reachable by gdb but the kernel segfaults somewhere in the middle of operation indicates things are fundamentally wrong with over how much data

[Discuss-gnuradio] segfault in volk_32f_x2_dot_prod_32f_a_generic

Hello and thank you for the gnuradio project! Seems like this mailing list silently drops the messages from non-subscribers, that is not mentioned in . I'm trying to use an AM Demod block but encounter a segfault:

Re: [Discuss-gnuradio] Exports in _runtime_swig.pyd

I wrote: Thus functions/vars in _runtime_swig.pyd gets a dllexport linkage. But comparing to gnuradio-runtime/swig/pmt_swig.i there is no PMT_API at the top. Why the difference? Further to the problem I had with linking in the Swig code for this: extern const pmt_t PMT_T; (in pmt_swig.i) Th

[Discuss-gnuradio] Exports in _runtime_swig.pyd

I'm still trying to understand the build-process and internals of GnuRadio. While trying to build the Swig .pyd modules, I notice that gnuradio-runtime/swig/runtime_swig.i has a: #define GR_RUNTIME_API Thus functions/vars in _runtime_swig.pyd gets a dllexport linkage. But comparing to gnuradio