[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Discuss-gnuradio] Segfault with volk on 32 bit AMD

From: Tom Rondeau
Subject: Re: [Discuss-gnuradio] Segfault with volk on 32 bit AMD
Date: Fri, 16 Mar 2012 13:35:39 -0400

On Fri, Mar 16, 2012 at 11:38 AM, Frederick Stevens <address@hidden> wrote:

Not sure if this is the right place to post this but I have had this error with 3.5.2 and later (git and on Slackware 13.37 on a dual athlon 32 bit machine.  The problem is not present on an Intel Atom (32 bit dual core) machine with exactly the same configuration and libraries installed.  Here is the python error report from gnuradio-companion:

Executing: "/home/fred/gnuradio/top_block.py"

Using Volk machine: generic
Traceback (most recent call last):
 File "/home/fred/gnuradio/top_block.py", line 169, in <module>
   tb = top_block()
 File "/home/fred/gnuradio/top_block.py", line 101, in __init__
   self.gr_multiply_xx_3 = gr.multiply_vff(1)
 File "/usr/lib/python2.6/site-packages/gnuradio/gr/gnuradio_core_general.py", line 8783, in multiply_ff
   return _gnuradio_core_general.multiply_ff(vlen)
RuntimeError: gr_block::set_alignment_multiple

When running volk_profile from the git sources, the application produces a segfault when it reaches volk_32fc_x2_multiply_32fc_a

I did a trace using ddd and it traced the error back to libvolk.so.0.0.0



Well, that doesn't make me happy at all. Especially since we just patched the release yesterday...

Sounds like the AMD chip is handling something wrong (or differently) with the alignment. All vectors passed using volk_profile are supposed to be properly byte aligned.

Fred, can you just check for me what happens when you run it under gdb? Just run "gdb volk_profile" and when it crashes, do a "bt" and post the results of the backtrace here.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]