Hi,

yes, this is how it is supposed to look. But please read the posts at the bottom of the thread. Actually, it should work without modifications now.

Best,
Bastian

On 08/13/2015 04:03 PM, Tian Alvin wrote:
Hi Bastian,

I followed the suggestion on github:

*Use*

"std::string temp = (boost::format("encoding: %1% - length: %2% -
symbols: %3%")
% d_encoding % d_len % d_copy_symbols).str();
//mylog(temp);"

*to change* : in the ofdm_decode_signal.cc# L197&L198
"mylog(boost::format("encoding: %1% - length: %2% - symbols: %3%")
% d_encoding % d_len % d_copy_symbols);"

Now I can get the below result:

Inline image 1

Does this mean the flow graph has been run correctly?

Paul----Thank you very much for your suggestion and sharing!



On Thu, Aug 13, 2015 at 1:59 PM, Bastian Bloessl <bloe...@ccs-labs.org
<mailto:bloe...@ccs-labs.org>> wrote:

    Hi,

    I just replied on github

    https://github.com/bastibl/gr-ieee802-11/issues/18#issuecomment-130651522

    It would be great if you could try what I suggest there.

    Best,
    Bastian

    On 08/13/2015 02:32 PM, Garver, Paul W wrote:

        Make sure logging is disabled on ALL blocks. I haven't seen that
        libstdcxx error before, but I do have the segfaults with the
        logging in
        Ubuntu 15.04 with pybombs install.

        Paul Garver


        On Aug 13, 2015, at 7:33 AM, Tian Alvin <tianye000...@gmail.com
        <mailto:tianye000...@gmail.com>
        <mailto:tianye000...@gmail.com <mailto:tianye000...@gmail.com>>>
        wrote:

            Hi Paul,

            Thanks very much for your help! I have disabled logging and
            debug in
            OFDM Parse MAC block, but the error is still there.

            Did you also see the below error in your case when (gdb) run
            wifi_loopback.py?
            <image.png>
            ImportError: No module named 'libstdcxx'


            Thanks


            On Wed, Aug 12, 2015 at 9:07 PM, Paul Garver
            <garv...@gatech.edu <mailto:garv...@gatech.edu>
            <mailto:garv...@gatech.edu <mailto:garv...@gatech.edu>>> wrote:

                 Tian,

                 Disable logging and debug in the GRC flowgraph.  See if
            this
                 solves the problem. For reference, see [1].


                 [1]
            
https://lists.gnu.org/archive/html/discuss-gnuradio/2015-07/msg00289.html

                 On 08/12/2015 01:23 PM,
            discuss-gnuradio-requ...@gnu.org
            <mailto:discuss-gnuradio-requ...@gnu.org>
                 <mailto:discuss-gnuradio-requ...@gnu.org
            <mailto:discuss-gnuradio-requ...@gnu.org>> wrote:

                     Send Discuss-gnuradio mailing list submissions to
                discuss-gnuradio@gnu.org
                <mailto:discuss-gnuradio@gnu.org>
                <mailto:discuss-gnuradio@gnu.org
                <mailto:discuss-gnuradio@gnu.org>>

                     To subscribe or unsubscribe via the World Wide Web,
                visit
                https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
                     or, via email, send a message with subject or body
                'help' to
                discuss-gnuradio-requ...@gnu.org
                <mailto:discuss-gnuradio-requ...@gnu.org>
                <mailto:discuss-gnuradio-requ...@gnu.org
                <mailto:discuss-gnuradio-requ...@gnu.org>>

                     You can reach the person managing the list at
                discuss-gnuradio-ow...@gnu.org
                <mailto:discuss-gnuradio-ow...@gnu.org>
                <mailto:discuss-gnuradio-ow...@gnu.org
                <mailto:discuss-gnuradio-ow...@gnu.org>>

                     When replying, please edit your Subject line so it
                is more specific
                     than "Re: Contents of Discuss-gnuradio digest..."


                     Today's Topics:

                         1. error with running wifi_loopback.grc from
                gr-ieee802-11
                            (Tian Alvin)


                     _______________________________________________
                     Discuss-gnuradio mailing list
                Discuss-gnuradio@gnu.org
                <mailto:Discuss-gnuradio@gnu.org>
                <mailto:Discuss-gnuradio@gnu.org
                <mailto:Discuss-gnuradio@gnu.org>>
                https://lists.gnu.org/mailman/listinfo/discuss-gnuradio



                 _______________________________________________
                 Discuss-gnuradio mailing list
            Discuss-gnuradio@gnu.org <mailto:Discuss-gnuradio@gnu.org>
            <mailto:Discuss-gnuradio@gnu.org
            <mailto:Discuss-gnuradio@gnu.org>>
            https://lists.gnu.org/mailman/listinfo/discuss-gnuradio




        _______________________________________________
        Discuss-gnuradio mailing list
        Discuss-gnuradio@gnu.org <mailto:Discuss-gnuradio@gnu.org>
        https://lists.gnu.org/mailman/listinfo/discuss-gnuradio


    --
    Dipl.-Inform. Bastian Bloessl
    Distributed Embedded Systems
    University of Paderborn, Germany
    http://www.ccs-labs.org/~bloessl/



--
Dipl.-Inform. Bastian Bloessl
Distributed Embedded Systems
University of Paderborn, Germany
http://www.ccs-labs.org/~bloessl/

_______________________________________________
Discuss-gnuradio mailing list
Discuss-gnuradio@gnu.org
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Reply via email to