From: Jan Vroonhof <vroonhof@math.ethz.ch>
Cc: xemacs-beta@xemacs.org, ding@gnus.org
Subject: Re: crash
Date: 03 Mar 2000 09:39:39 +0100 [thread overview]
Message-ID: <byog8wmoqc.fsf@bolzano.math.ethz.ch> (raw)
In-Reply-To: Michael Harnois's message of "02 Mar 2000 14:06:14 -0600"
Michael Harnois <mdharnois@home.com> writes:
> > You did say you could reproduce this?
>
> Every time. I reproduced it just for you ...
Well thank you :-). You seem to be the first with a reproducible
problem in this area. Would you mind tarring your whole setup up for
when I have more time (I don't ATM :-().
Jan
What happens when you decrease or increase max-specpdl-size?
next prev parent reply other threads:[~2000-03-03 8:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-01 3:59 crash Michael Harnois
2000-03-01 8:13 ` crash Jan Vroonhof
2000-03-01 14:54 ` Identifying CVS version (was: Re: crash) lconrad
2000-03-01 23:00 ` Neil Crellin
2000-03-03 17:33 ` Jan Vroonhof
2000-03-02 15:38 ` crash Michael Harnois
2000-03-02 17:01 ` crash Jan Vroonhof
2000-03-02 20:06 ` crash Michael Harnois
2000-03-03 8:39 ` Jan Vroonhof [this message]
2000-03-03 15:13 ` crash Michael Harnois
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=byog8wmoqc.fsf@bolzano.math.ethz.ch \
--to=vroonhof@math.ethz.ch \
--cc=ding@gnus.org \
--cc=xemacs-beta@xemacs.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).