u.org
> ] *On Behalf
> Of *Marcus Müller
> *Sent:* Wednesday, May 24, 2017 12:26 PM
> *To:* discuss-gnuradio@gnu.org; Philip Balister
>
> *Subject:* Re: [Discuss-gnuradio] Custom C++ blocks on E310
>
>
>
> Hi Jessica,
>
> that's really interesting!
>
>
nuradio
> [mailto:discuss-gnuradio-bounces+jessica.iwamoto=aero@gnu.org] *On
> Behalf Of *Marcus Müller
> *Sent:* Wednesday, May 24, 2017 12:26 PM
> *To:* discuss-gnuradio@gnu.org; Philip Balister
> *Subject:* Re: [Discuss-gnuradio] Custom C++ blocks on E310
>
>
>
&g
uss-gnuradio@gnu.org; Philip Balister
Subject: Re: [Discuss-gnuradio] Custom C++ blocks on E310
Hi Jessica,
that's really interesting!
It means that the problem only happens when you use your compiler to build your
C++ blocks, but not when only using the GNU Radio that's already part
> *Sent:* Monday, May 15, 2017 8:38 AM
> *To:* Ben Hilburn
> *Cc:* discuss-gnuradio@gnu.org
> *Subject:* [WARNING: SPOOFED E-MAIL--Non-Aerospace Sender] Re:
> [Discuss-gnuradio] Custom C++ blocks on E310
>
>
>
> Hi Ben,
>
>
>
> Here is some of the backtrace f
, 2017 8:38 AM
To: Ben Hilburn
Cc: discuss-gnuradio@gnu.org
Subject: [WARNING: SPOOFED E-MAIL--Non-Aerospace Sender] Re: [Discuss-gnuradio]
Custom C++ blocks on E310
Hi Ben,
Here is some of the backtrace from the error. At the top level, the error
starts in the msg_connect function and it looks
/runtime_swigPYTHON_wrap.cxx:47551
Thanks,
Jessica
From: Ben Hilburn [mailto:bhilb...@gnuradio.org]
Sent: Friday, May 12, 2017 1:35 PM
To: Jessica Iwamoto
Cc: discuss-gnuradio@gnu.org
Subject: Re: [Discuss-gnuradio] Custom C++ blocks on E310
Hey Jessica -
The SIGBUS you are receiving indicates that there is likely
Hey Jessica -
The SIGBUS you are receiving indicates that there is likely some funniness
happening with memory addressing / access somewhere. Especially since your
test flowgraph is so simple, using GDB to get a backtrace might point you
to the offending code pretty quickly. For more details on ho
Hi again,
Attached is the code that I'm using if anyone would like to try to replicate my
issue. The test_msg_py.py file contains the custom python block code for a
simple message sink. The test_msg_impl.cc, test_msg_impl.h, and test_msg.h
files contain the custom C++ code for a message sink. T