I'll give it a try (more than willing) but you will have to point me
to the files to insert the debug print statements and the buffers to
use as I am very new to c++ and know only enough c code to be
dangerous if left to myself. Usually have my nose in some assembler
and used to do a lot of forth. I do make judicious use of man pages
and HOWTO help though.|
On 03/19/2012 08:10 AM, Tom Rondeau wrote:
On Sun, Mar 18, 2012 at 8:00 PM,
Frederick Stevens <address@hidden>
Volk_profile ran to
completion. I am using the git source tree updated just
before I did the run. I commented out line 38 of
volk_profile.cc as you suggested and ran volk_profile under
gdb. The output is in the attached text file. I have also
attached the generated volk_config from ~/.volk/volk_config.
Thanks. Strange that it's just that kernel, then. Can you
put in some debug lines that will print out the size of the
buffers being used and the 'number' variable in
volk_32fc_x2_multiply_32fc_a when the crash occurs. I just
want to see if the loop is trying to go beyond the bounds of
I noted from running
gnuradio-companion version 3.5.1, (which works) that when I
use a multiply block, this message from python is generated:
>>> gr_fir_fff: using 3DNow!
but volk_profile does not seem to recognize the 3DNow!
processor extensions (produces sse2 and sse3 messages on the
Intel Atom 32 bit machine).
Yeah, that's fine. Without a 3DNow! kernel, Volk will just
fall back on the generic implementation. The thought being
that the generic version will work for everyone. So we need to
figure out why that's not true for your...
Hope this helps! Let
me know if you want me to try anything else. I'll let you
know how things turn out on the other machine as well.
On 03/18/2012 04:31 PM, Tom Rondeau wrote:
On Fri, Mar 16, 2012 at 6:11
PM, Frederick Stevens <address@hidden>
a few restarts, here is my output. I did a
fresh pull from git because I was getting some
errors with missing *.h files in gruel/src/swig
or something like that. Hope this helps!
Program received signal SIGSEGV, Segmentation
74 *cPtr++ = (*aPtr++) * (*bPtr++);
#0 0xb7edbb74 in
Alright, Fred, definitely something strange
going on here. My only guess is that for some
reason on your architecture/OS/whatever, something
is being handled incorrectly and the buffers a, b,
and c are not getting generated correctly, maybe
something like it's not doubling the number of
items for the complex data type (before this
function test, there are 16ic, or complex shorts,
being tested, but this is the first complex float
It's hard to tell if it's something about it
being an AMD chip, 32-bit, Slackware version, gcc
version, etc. And I don't have an AMD chip to test
on, but I could load up a 32-bit Slackware VM at
How much work are you willing to put into this
to help us nail this down?
If you can follow through the volk_profile test
code, we can start outputting more debug info. To
start with, I'd suggest going into
volk/apps/volk_profile.cc and commenting out line
38, rebuild the application, and run this new
volk_profile to see if it fails on any other
Discuss-gnuradio mailing list