This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: fix sjlj eh vs dwarf2 debug


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.
>
> 	Andrew
>
> (1) because as far as I can tell, no one has extended GDB's
>     throw/catch code (contributed by HP) to support anything beyond
>     HP's C++ compiler.

Err, look at a patch i submitted about a year ago to extend it to
support gcc's throw/catch model through stupid stack frame tricks and
breakpointing __throw and __catch.

>

-- 
"I went down the street to the 24-hour grocery.  When I got
there, the guy was locking the front door.  I said, "Hey, the
sign says you're open 24 hours."  He said, "Yes, but not in a
row."
"-Steven Wright


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]