This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
gdb/575: Don't use setjmp / longjmp, use catch_exceptions() et.al.?
- From: ac131313 at redhat dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 18 Jun 2002 14:20:53 -0000
- Subject: gdb/575: Don't use setjmp / longjmp, use catch_exceptions() et.al.?
- Reply-to: ac131313 at redhat dot 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: