From: "Petr Hluzín" <petr.hluzin@gmail.com>
To: Brian Heilig <bheilig@etinternational.com>
Cc: gdb <gdb@sourceware.org>
Subject: Re: Assertion Fail: FDE != NULL in Cyclops64
Date: Tue, 23 Nov 2010 21:17:00 -0000 [thread overview]
Message-ID: <AANLkTinEK1vpvtAMZbb6T8aq7gKA7JbSjn-BRy8-C09O@mail.gmail.com> (raw)
In-Reply-To: <1290438965.1567.22.camel@random>
Hello
On 22 November 2010 16:16, Brian Heilig <bheilig@etinternational.com> 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.)
--
Petr Hluzin
prev parent reply other threads:[~2010-11-23 21:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-22 15:16 Brian Heilig
2010-11-23 21:13 ` Tom Tromey
2010-11-23 21:17 ` Petr Hluzín [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTinEK1vpvtAMZbb6T8aq7gKA7JbSjn-BRy8-C09O@mail.gmail.com \
--to=petr.hluzin@gmail.com \
--cc=bheilig@etinternational.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox