Use Valgrind or Electric Fence to find your memory overrun. It's not where
that malloc is, but it is overwriting the malloc memory, thus GDB blows up
in malloc().
On Wed, Jan 3, 2018 at 1:52 PM, Steve <coupaydevi...@gmail.com> wrote:
> If anyone clicked the link, it took you to a movie that showed my
> Discovery board with the ring of death. Just some new years humour...
>
> Mysteriously, when I step through the code with GDB it blows up on a
> malloc() in fdmdv_create().
>
> This is strange, as the exact same code exists on the standard sm1000
> code, and after stepping through the malloc() it does fine.
>
> Obviously, my code must not be (really) the same, and I gimped the
> initialization somewhere.
>
> Happy New Year
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Freetel-codec2 mailing list
> Freetel-codec2@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freetel-codec2
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Freetel-codec2 mailing list
Freetel-codec2@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freetel-codec2
