From: Michal Ludvig <mludvig@suse.cz>
To: Richard Henderson <rth@redhat.com>
Cc: gcc@gcc.gnu.org, gdb <gdb@sources.redhat.com>
Subject: Re: What is LSDA?
Date: Thu, 30 May 2002 00:42:00 -0000 [thread overview]
Message-ID: <3CF5D7D7.40107@suse.cz> (raw)
In-Reply-To: <20020529110320.I4168@redhat.com>
Richard Henderson wrote:
> On Wed, May 29, 2002 at 02:41:24PM +0200, Michal Ludvig wrote:
>
>>In dwarf-2 debug_frame generated by GCC 3.1 I can sometimes see an
>>augmentation "L"...
>
> Wait.. You're seeing this in .debug_frame? That's not right.
> It should only be present in .eh_frame.
You're right. It appears in .eh_frame only.
What other differences can I expect between eh_frame and debug_frame?
For now I handle both of them almost in the same way.
Exceptions are: Different CIE-id, different way of finding the right CIE
for a given FDE, and from now on ignoring LSDA in eh_frame.
Is there something else?
Michal Ludvig
--
* SuSE CR, s.r.o * mludvig@suse.cz
* +420 2 9654 5373 * http://www.suse.cz
next prev parent reply other threads:[~2002-05-30 7:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-29 5:41 Michal Ludvig
2002-05-29 11:02 ` Richard Henderson
2002-05-29 11:03 ` Richard Henderson
2002-05-30 0:42 ` Michal Ludvig [this message]
2002-05-30 3:12 ` Richard Henderson
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=3CF5D7D7.40107@suse.cz \
--to=mludvig@suse.cz \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=rth@redhat.com \
/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