public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jason Merrill <jason_merrill@redhat.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Richard Henderson <rth@redhat.com>,
	gcc-patches@gcc.gnu.org, mark@codesourcery.com,
	gdb@sources.redhat.com
Subject: Re: fix sjlj eh vs dwarf2 debug
Date: Thu, 23 Aug 2001 03:19:00 -0000	[thread overview]
Message-ID: <m3heuzuliy.fsf@prospero.cambridge.redhat.com> (raw)
In-Reply-To: <3B847864.7060106@cygnus.com>

>>>>> "Andrew" == Andrew Cagney <ac131313@cygnus.com> writes:

>>>>>>> "Richard" == Richard Henderson <rth@redhat.com> writes:
>> 
>>> On Tue, Aug 14, 2001 at 12:16:28PM -0700, Richard Henderson wrote:
>> 
>>>> * dwarf2out.c (dwarf2out_frame_finish): Never emit .eh_frame
>>>> if USING_SJLJ_EXCEPTIONS.
>> 
>>> Actually, I take that back.  Now that we are (or may be) encoding
>>> .eh_frame data in non-standard ways, we should probably not try to
>>> emit only one of .eh_frame or .debug_frame.  That way the debugger
>>> doesn't have to care about whatever funnies we do with augmentation.
>> 
>>> Jason, what are your thoughts?
>> That makes sense to me.  What do gdb folks think?

> This won't affect GDB(1). I'd go with what ever the current interpretation
> of the standards are.

.debug_frame is part of the DWARF 2 standard; .eh_frame is our own
modification of that format for use in a loaded section, for which there is
no standard but gcc.

Jason

  parent reply	other threads:[~2001-08-23  3:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-14 12:16 Richard Henderson
2001-08-14 12:19 ` Richard Henderson
2001-08-15  3:03   ` Jason Merrill
2001-08-22 20:29     ` Andrew Cagney
2001-08-23  0:30       ` Richard Henderson
2001-08-23  3:19       ` Jason Merrill [this message]
2001-08-23  4:26       ` Daniel Berlin

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=m3heuzuliy.fsf@prospero.cambridge.redhat.com \
    --to=jason_merrill@redhat.com \
    --cc=ac131313@cygnus.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb@sources.redhat.com \
    --cc=mark@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).