From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: eller.helmut@gmail.com, 9463@debbugs.gnu.org
Subject: bug#9463: 24.0.50; Errors should not be continuable
Date: Fri, 09 Sep 2011 10:10:49 +0300 [thread overview]
Message-ID: <83vct25gxy.fsf@gnu.org> (raw)
In-Reply-To: <jwvhb4mv4pa.fsf-monnier+emacs@gnu.org>
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Date: Thu, 08 Sep 2011 22:23:09 -0400
> Cc: 9463@debbugs.gnu.org
>
> > I think the "do what would have happened if the debugger had not been
> > called" thing should be a different command, like resignal or abort.
>
> Why? When the debugger is called in a non-error case, the "c" does just
> that "do whatever would have happened if the debug call had no taken place".
>
> > c should only continue from truly continuable situations, like
> > breakpoints.
>
> Again: why?
I agree with Stefan. The current operation of `c' is consistent with
what other debuggers do in this situation. For example, when GDB
catches a fatal signal, typing `c' will simply let the program
continue with the signal, which may mean it will crash.
next prev parent reply other threads:[~2011-09-09 7:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-08 12:01 bug#9463: 24.0.50; Errors should not be continuable Helmut Eller
2011-09-08 13:31 ` Stefan Monnier
2011-09-08 18:13 ` Helmut Eller
2011-09-09 2:23 ` Stefan Monnier
2011-09-09 6:53 ` Helmut Eller
2011-09-09 14:07 ` Stefan Monnier
2011-09-09 16:37 ` Helmut Eller
2011-09-09 21:44 ` Stefan Monnier
2011-09-10 18:27 ` Helmut Eller
2011-09-19 21:17 ` Stefan Monnier
2011-09-20 6:49 ` Helmut Eller
2011-09-20 21:53 ` Stefan Monnier
2011-09-21 8:05 ` Helmut Eller
2011-09-21 19:09 ` Stefan Monnier
2011-09-21 19:53 ` Helmut Eller
2012-02-22 2:20 ` Glenn Morris
2011-09-09 7:10 ` Eli Zaretskii [this message]
2011-09-09 7:36 ` Helmut Eller
2011-09-09 7:59 ` Eli Zaretskii
2011-09-09 8:22 ` Helmut Eller
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=83vct25gxy.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=9463@debbugs.gnu.org \
--cc=eller.helmut@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.