* Re: fix sjlj eh vs dwarf2 debug
2001-08-22 20:29 ` Andrew Cagney
@ 2001-08-23 0:30 ` Richard Henderson
2001-08-23 3:19 ` Jason Merrill
2001-08-23 4:26 ` Daniel Berlin
2 siblings, 0 replies; 5+ messages in thread
From: Richard Henderson @ 2001-08-23 0:30 UTC (permalink / raw)
To: Andrew Cagney; +Cc: Jason Merrill, gcc-patches, mark, gdb
On Wed, Aug 22, 2001 at 11:28:36PM -0400, Andrew Cagney wrote:
> (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.
That is actually irrelevant. The place gdb should be using .debug_frame
is instead of code reading for the prologue.
r~
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: fix sjlj eh vs dwarf2 debug
2001-08-22 20:29 ` Andrew Cagney
2001-08-23 0:30 ` Richard Henderson
@ 2001-08-23 3:19 ` Jason Merrill
2001-08-23 4:26 ` Daniel Berlin
2 siblings, 0 replies; 5+ messages in thread
From: Jason Merrill @ 2001-08-23 3:19 UTC (permalink / raw)
To: Andrew Cagney; +Cc: Richard Henderson, gcc-patches, mark, gdb
>>>>> "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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: fix sjlj eh vs dwarf2 debug
2001-08-22 20:29 ` Andrew Cagney
2001-08-23 0:30 ` Richard Henderson
2001-08-23 3:19 ` Jason Merrill
@ 2001-08-23 4:26 ` Daniel Berlin
2 siblings, 0 replies; 5+ messages in thread
From: Daniel Berlin @ 2001-08-23 4:26 UTC (permalink / raw)
To: Andrew Cagney; +Cc: Jason Merrill, Richard Henderson, gcc-patches, mark, gdb
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
^ permalink raw reply [flat|nested] 5+ messages in thread