[Fwd: gdb/575: Don't use setjmp / longjmp, use catch_exceptions() et.al.?]

[Fwd: gdb/575: Don't use setjmp / longjmp, use catch_exceptions() et.al.?]

[Andrew Cagney]

[-- Attachment #1: Type: text/plain, Size: 201 bytes --]

Hello,

Just stumbled across this.

GDB eliminated most of the setjmp() / longjmp()'s long ago.  I think I 
should formalize this as part of the internals doco and add it to the ARI.

thoughts?
Andrew

[-- Attachment #2: gdb/575: Don't use setjmp / longjmp, use catch_exceptions() et.al.? --]
[-- Type: message/rfc822, Size: 3158 bytes --]

From: ac131313@redhat.com
To: gdb-gnats@sources.redhat.com
Subject: gdb/575: Don't use setjmp / longjmp, use catch_exceptions() et.al.?
Date: 18 Jun 2002 14:20:53 -0000
Message-ID: <20020618142053.26465.qmail@sources.redhat.com>


>Number:         575
>Category:       gdb
>Synopsis:       Don't use setjmp / longjmp, use catch_exceptions() et.al.?
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Tue Jun 18 07:28:03 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     ac131313@redhat.com
>Release:        2002-06-18
>Organization:
>Environment:

>Description:
The functions catch_exceptions() and throw_exception() are provided for handling cases where a stack unwind (exception) is needed.  These mechanisms, tie in with gdb's cleanups ensuring that the stack is unwound cleanly.

New code should use these mechanisms and not setjmp() / longjmp().

Needs style doco
Needs ari

>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:

Re: [Fwd: gdb/575: Don't use setjmp / longjmp, use catch_exceptions() et.al.?]

[Eli Zaretskii]

On Tue, 18 Jun 2002, Andrew Cagney wrote:

> GDB eliminated most of the setjmp() / longjmp()'s long ago.  I think I 
> should formalize this as part of the internals doco and add it to the ARI.
> 
> thoughts?

Yes, I agree.