discuss-gnuradio
[Top][All Lists]
Advanced

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

Re: [Discuss-gnuradio] crashes, memory errors and valgrind


From: Tom Rondeau
Subject: Re: [Discuss-gnuradio] crashes, memory errors and valgrind
Date: Sun, 3 Jun 2012 11:12:24 -0400

On Sat, Jun 2, 2012 at 5:50 AM, Patrick Strasser
<address@hidden> wrote:
> Hello list,
>
> I'm playing around with gqrx, an excellent example which great
> standalone software can be built with gnuradio.
>
> I'm running phirsch's rtlsdr fork, do not have a Funcube Dongle or USRP
> at hand, but rather a Terratex NOXON DAB stick - 25€ part does the trick
> fine enough for me ;-)
>
> I'm running a self-compiled gnuradio rev3.6.0 on my Debian testing amd64
> machine.
>
> Sometime it crashes with messages like "glibc detected *** gqrx:
> corrupted double-linked list". Firing up valgrind on it I find -besides
> several uninitialized variables- messages of the kind:
>
> ==31294== Invalid read of size 8
> ==31294==    at 0x4F782AC: float_dotprod_sse (in
> /usr/local/lib/libgnuradio-core-3.6.0.so.0.0.0)
> [deleted some lines...]
> ==31294==  Address 0x1a211ba8 is 440 bytes inside a block of size 447
> alloc'd
> ==31294==    at 0x402894D: malloc (in
> /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
> ==31294==    by 0x4FB3C5E: malloc16Align (in
> /usr/local/lib/libgnuradio-core-3.6.0.so.0.0.0)
> ==31294==    by 0x4FB3CA9: calloc16Align (in
> /usr/local/lib/libgnuradio-core-3.6.0.so.0.0.0)
> ==31294==    by 0x4F75E27: gr_fir_fff_simd::set_taps(std::vector<float,
> std::allocator<float> > const&) (in
> /usr/local/lib/libgnuradio-core-3.6.0.so.0.0.0)
> [deleted some lines...]
>
> Full trace of that error below, I can provide a full trace of a run if
> needed.
>
> Usually the program runs stable, but occasionally it crashes. I played
> around with the internal bandwidth to get better FM reception - 75kHz is
> quite narrow for FM reception. This change seems to trigger the problems
> much faster. I hardly can change any parameters while running without a
> crash.
>
> I'm no expert, but it seems to me there is not enough memory allocated.
> Maybe an off-by-one error? Did anyone see things like that or used
> valgrind recently on gnuradio programs? What could I do to find out more
> about this problem?
>
> Regards
>
> Patrick
>
> ---------------------------------------------------------
>
> ==31294== Invalid read of size 8
> ==31294==    at 0x4F782AC: float_dotprod_sse (in
> /usr/local/lib/libgnuradio-core-3.6.0.so.0.0.0)
> ==31294==    by 0x4F8A27F:
> gr_rational_resampler_base_fff::general_work(int, std::vector<int,


Patrick,

It looks like you're problem is in the rational_resampler code. I
wonder if there's something about the resampling rate being used
that's causing something to go out of bounds here. Can you dig into
the code and figure out what interpolation and decimation rates are
being used?

Tom



reply via email to

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