I need to find why fftw is segfaulting, in an application which built OK on 32-bit target with gcc4.0 and now fails on a 64-bit target with gcc4.6.
The fftw configure options:
- –enable-debug
- –enable-debug-malloc
- –enable-debug-alignment
only appear to add internal debug, I was hoping to get somewhere by turning on gdb debug symbols so I can try to trace the cause of the segfault. Is there an option for gdb debug that I’ve missed somehow?
Alternatively, is there any other way I should be trying to track down a segfault in fftw?
As noted in my comments above, the answer was to edit the Makefile produced by fftw3’s configure to add -ggdb to the CFLAGS.