From: Andrew Cagney <ac131313@cygnus.com>
To: gdb@sources.redhat.com
Subject: [Fwd: gdb/575: Don't use setjmp / longjmp, use catch_exceptions() et.al.?]
Date: Tue, 18 Jun 2002 07:38:00 -0000 [thread overview]
Message-ID: <3D0F45C9.6030401@cygnus.com> (raw)
[-- 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:
next reply other threads:[~2002-06-18 14:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-18 7:38 Andrew Cagney [this message]
2002-06-18 22:12 ` Eli Zaretskii
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=3D0F45C9.6030401@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb@sources.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