From: Steve Kemp <steve@steve.org.uk>
To: 27585@debbugs.gnu.org
Subject: bug#27585: segfault when evaluating a file containing only backticks
Date: Thu, 06 Jul 2017 03:46:35 +0000 [thread overview]
Message-ID: <1499312795.32152.3@ssh.steve.org.uk> (raw)
In-Reply-To: <83tw2qmzsl.fsf@gnu.org>
> > I expect evaluating lisp to not kill the editor
>
> Valid Lisp, I agree. But yours isn't.
Here we disagree.
I enjoy reporting bugs when invalid things are tried, because I
expect software to be robust, or as much as possible. If you feed
invalid script to gawk, perl, emacs, etc, etc, I expect an error
not a segfault.
I appreciate there are often difficult cases, such as infinite
recursion, division by zero, and memory exhaustion, but the idea
that ones programming environment is free to crash if your code
is wrong is .. unpleasant.
> > In the real world? Nobody.
>
> Then why are we discussing this use case? Let's talk about
> more practical and interesting cases.
I read from this that I should not bother running any more
fuzzing, after all if it does result in any crashes they're a result
of bogus-coding that would never be hit in the real world.
That's unfortunate, but I've no particular wish to argue
in public. I will follow your suggestion.
Bug left open because it crashes for me, if it fails to crash
for others with a somewhat reasonable error message I guess
that is good.
Steve
--
next prev parent reply other threads:[~2017-07-06 3:46 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 6:21 bug#27585: segfault when evaluating a file containing only backticks Steve Kemp
2017-07-05 7:51 ` Andreas Schwab
2017-07-05 8:26 ` Steve Kemp
2017-07-05 18:41 ` Eli Zaretskii
2017-07-05 18:55 ` Steve Kemp
2017-07-05 19:47 ` Eli Zaretskii
2017-07-06 3:46 ` Steve Kemp [this message]
2017-07-06 15:16 ` Eli Zaretskii
2017-07-06 15:33 ` Steve Kemp
2017-07-06 16:24 ` Eli Zaretskii
2017-07-06 6:46 ` Andreas Schwab
2017-07-06 15:19 ` Eli Zaretskii
2017-07-06 15:31 ` Andreas Schwab
2017-07-06 15:37 ` Eli Zaretskii
2017-07-06 15:41 ` Andreas Schwab
2017-07-06 15:52 ` Daniel Colascione
2017-07-06 16:19 ` Eli Zaretskii
2017-07-06 16:37 ` Daniel Colascione
2017-07-06 17:27 ` Eli Zaretskii
2017-07-06 15:48 ` Daniel Colascione
2017-07-14 12:09 ` Paul Eggert
2017-07-14 13:30 ` Eli Zaretskii
2017-07-15 5:03 ` Steve Kemp
2017-07-15 5:12 ` Paul Eggert
2017-07-15 7:15 ` 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=1499312795.32152.3@ssh.steve.org.uk \
--to=steve@steve.org.uk \
--cc=27585@debbugs.gnu.org \
/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.