This is the mail archive of the
mailing list for the GDB project.
Re: Assertion Fail: FDE != NULL in Cyclops64
- From: Petr HluzÃn <petr dot hluzin at gmail dot com>
- To: Brian Heilig <bheilig at etinternational dot com>
- Cc: gdb <gdb at sourceware dot org>
- Date: Tue, 23 Nov 2010 22:16:38 +0100
- Subject: Re: Assertion Fail: FDE != NULL in Cyclops64
- References: <1290438965.1567.22.camel@random>
On 22 November 2010 16:16, Brian Heilig <firstname.lastname@example.org> wrote:
> I found that memmove (and other functions) were not compiled with debug
> information. Since these were hand optimized routines in assembly it
> would be very difficult to add debugging information.
What kind of debugging information to add?
Source lines? GAS has an option to include these. It has to be enabled
manually, GCC does not pass -g option for some reason.
Type information? I dunno.
Stack-trace/-unwind info? I think this should be easy. The feature is
well hidden in GAS. I fact it is not supported on some architectures
and the docs do not say which. (I got burnt.) If GAS implements them
then I might try to write the annotations for the memmove.
Where is the source for the memmove function?
Is it in-line assembly in C file or standalone asm file? (I assume standalone.)
(I know nothing about the assertion or its surrounding code.)