Oh, fft_r[] and fft_l[] are similar memory areas from calloc which
hold the FFT output data once it's moved from the fft3w output array.
I pick left and right channels out of the PCM data and FFT them
individually, then plot them separately on the same frame image.
On 5/6/21, Alan Corey
This is under Debian Bullseye Linux on a PineBook Pro so ARM 64-bit I
think although sizeof(int) is still 4. It's a fairly complicated
program at 750 lines in it's almost-done state so I'm not posting the
whole thing. I have this program that does audiograms
https://sourceforge.net/projects/audi
Those happen, don't take it personally. They used to be real common
in ARM. Sounds like you hit a code that's not covered. Not that I'm
one that can add it.
See the "==466== Your program just tried to execute an instruction that Valgrind
==466== did not recognise." section of the error message
lgrind-dbg 1:3.12.0~svn20160714-1+b1
arm64instrumentation framework for building
dynamic analysis tools (debug)
ii valkyrie 2.0.0-1+b1
arm64open-source graphical user interface for the
Valgrind
On 9/30/19, Alan Corey wr
just used a Linux Mint VM:
>>>
>>> Other than Linux headers I only get this:
>>>
>>> $ dpkg -S /usr/include/x86_64-linux-gnu/asm/types.h
>>> linux-libc-dev:amd64: /usr/include/x86_64-linux-gnu/asm/types.h
>>>
>>> Should be package li
You're missing asm/types.h
Not sure what it's part of because there are 1 or 2 other types.h
files too. Somewhere in build-essentials or kernel building stuff I
picked it up. Try your kernel headers package I see:
locate asm/types.h
/usr/include/aarch64-linux-gnu/asm/types.h
/usr/src/linux-heade
A segfault is usually a bad pointer or something pointing outside
allocated space. Why it stops segfaulting when you run it through
Valgrind I don't know. Compile with -g for either Valgrind or gdb,
and if it still runs in Valgrind try gdb. You can just do gdb
then you'll probably have to type
I run it often on my Raspberry Pi 3b with 1 GB, never thought about it.
Sent from my Motorola XT1527
On Fri, Jan 25, 2019, 5:02 AM Padala Dileep wrote:
> Hi
>
> My system has 4GB memory ( arm-linux ) . But when I try to run the
> valgrind, the process becomes very slow, and it gets rebooted w
On 6/29/18, Edward Diener wrote:
> On 6/28/2018 9:01 PM, Alan Corey wrote:
>> I'm no expert, but especially if it's arm64 try fetching the absolute
>> latest from https://sourceware.org/git/gitweb.cgi?p=valgrind.git;a=summary
>>
>> That's about the erro
I'm no expert, but especially if it's arm64 try fetching the absolute
latest from https://sourceware.org/git/gitweb.cgi?p=valgrind.git;a=summary
That's about the error I got running versions before 3.13 on my Pi and
there was something similar even with 3.13 on the same Pi running as
arm64. (and
m64 Pi. I also
have a Rock64 which it should work on. I like these little arm boxes,
and my i386 machines are all 10+ years old by now
On 6/18/18, Ivo Raisr wrote:
> Il giorno lun 18 giu 2018 alle ore 15:57 Alan Corey
> ha scritto:
>>
>> Um, dumb question probably but you che
Um, dumb question probably but you checked it in where? Looks like
there are at least 4 forks of Valgrind on Github, on sourceware.org I
just see releases, nothing since 3.13.
On 6/18/18, Mark Wielaard wrote:
> On Sat, 2018-06-16 at 21:30 -0400, Alan Corey wrote:
>> OK, thanks, I ran
at 19:09 -0400, Alan Corey wrote:
>> > Linux version 4.16.0-2-arm64 (debian-ker...@lists.debian.org) (gcc
>> version 7.3.0 (Debian 7.3.0-19)) #1 SMP Debian 4.16.12-1 (2018-05-27)
>>
>> The Valgrind was a 3.13.0 that I'd built from the distribution
>> tarbal
mallocfree.c.
If that doesn't help, please report this bug to: www.valgrind.org
In the bug report, send all the above text, the valgrind
version, and what OS and version you are using. Thanks.
On 6/16/18, Tom Hughes wrote:
> On 16/06/18 17:49, Alan Corey wrote:
>
>> Maybe a
Maybe a bleeding edge version on Github or somewhere?
I'm on a Raspberry Pi 3b in 64 bit mode:
Linux version 4.16.0-1-arm64 (debian-ker...@lists.debian.org) (gcc
version 7.3.0 (Debian 7.3.0-17)) #1 SMP Debian 4.16.5-1 (2018-04-29)
I have Valgrind 3.13 I built from a release tarball, it works in 3
15 matches
Mail list logo
