bug#27585: Fwd: Re: bug#27585: segfault when evaluating a file containing only backticks

all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed

* bug#27585: Fwd: Re: bug#27585: segfault when evaluating a file containing only backticks
       [not found] <58232171-11ff-4d19-5107-0e705606d0e8@cs.ucla.edu>
@ 2017-09-24 22:47 ` Paul Eggert
  2017-09-29  8:32   ` CC'ing archived bugs (was: bug#27585: segfault when evaluating a file containing only backticks) Eli Zaretskii
  0 siblings, 1 reply; 3+ messages in thread
From: Paul Eggert @ 2017-09-24 22:47 UTC (permalink / raw
  To: 27585

[Sending this again since the bug was archived and read-only earlier today.]

-------- Forwarded Message --------
Subject: Re: bug#27585: segfault when evaluating a file containing only backticks
Date: Sun, 24 Sep 2017 11:32:44 -0700
From: Paul Eggert <eggert@cs.ucla.edu>

Philipp Stephani wrote:
> Paul Eggert <eggert@cs.ucla.edu> schrieb am Fr., 14. Juli 2017 um 14:10 Uhr:
> 
>> As Eli and Daniel mentioned, this area of Emacs cannot be 100% reliable
>>
> 
> Why? Surely Emacs could switch away from recursion for the reader and the
> evaluator to an explicitly-managed stack. That would be a bit of work, but
> certainly not impossible.

You are right, on both points. By "this area of Emacs" I was assuming the 
current recursive implementation. It's not the only place Emacs recurses, though.





^ permalink raw reply	[flat|nested] 3+ messages in thread

* CC'ing archived bugs (was: bug#27585: segfault when evaluating a file containing only backticks)
  2017-09-24 22:47 ` bug#27585: Fwd: Re: bug#27585: segfault when evaluating a file containing only backticks Paul Eggert
@ 2017-09-29  8:32   ` Eli Zaretskii
  2017-09-29 19:51     ` CC'ing archived bugs Paul Eggert
  0 siblings, 1 reply; 3+ messages in thread
From: Eli Zaretskii @ 2017-09-29  8:32 UTC (permalink / raw
  To: Paul Eggert; +Cc: emacs-devel

> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Sun, 24 Sep 2017 15:47:32 -0700
> 
> [Sending this again since the bug was archived and read-only earlier today.]

Which, btw, is one of my gripes about debbugs's defaults being utterly
unhelpful in these situations.  Is there any hope to change this to
anything more sane?



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: CC'ing archived bugs
  2017-09-29  8:32   ` CC'ing archived bugs (was: bug#27585: segfault when evaluating a file containing only backticks) Eli Zaretskii
@ 2017-09-29 19:51     ` Paul Eggert
  0 siblings, 0 replies; 3+ messages in thread
From: Paul Eggert @ 2017-09-29 19:51 UTC (permalink / raw
  To: Eli Zaretskii; +Cc: emacs-devel

On 09/29/2017 01:32 AM, Eli Zaretskii wrote:
> Which, btw, is one of my gripes about debbugs's defaults being utterly
> unhelpful in these situations.  Is there any hope to change this to
> anything more sane?

Sorry, I don't know.




^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2017-09-29 19:51 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <58232171-11ff-4d19-5107-0e705606d0e8@cs.ucla.edu>
2017-09-24 22:47 ` bug#27585: Fwd: Re: bug#27585: segfault when evaluating a file containing only backticks Paul Eggert
2017-09-29  8:32   ` CC'ing archived bugs (was: bug#27585: segfault when evaluating a file containing only backticks) Eli Zaretskii
2017-09-29 19:51     ` CC'ing archived bugs Paul Eggert

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.