From: Simon Josefsson <jas@extundo.com>
Subject: Re: "End of file during parsing" in Gcc handling
Date: Thu, 10 Oct 2002 22:23:41 +0200 [thread overview]
Message-ID: <ilun0pmdovm.fsf@h67n1c1o299.bredband.skanova.com> (raw)
In-Reply-To: <E17ziEX-0007kY-00@eris.void.at> (Andreas Fuchs's message of "Thu, 10 Oct 2002 20:40:29 +0200")
Andreas Fuchs <asf@void.at> writes:
> Today, Simon Josefsson <jas@extundo.com> wrote:
>>> I just tried to send a mail in recent CVS gnus, and a semi-recent CVS
>>> emacs (2002-10-06), to discover that when Gcc handling takes place, I
>>> get an error that is not traceable. toggle-debug-on-error did not
>>> reveal a backtrace. Stepping with edebug shows some _very_ weird
>>> behaviour:
>>
>> Perhaps (setq debug-on-signal t) gives a backtrace?
>
> Nope, and neither does -on-quit. I fear emacs is out of its mind. Or I
> am.
>
> I tried this with an older emacs (debian's) with current CVS gnus, and
> there the problem is present, too (but only when I load my gnus config
> )-:).
>
> The message doesn't seem to come from any of the gnus sources. WTF?
The error is from the emacs lisp reader, so most likely it is a
missing parentheses error or similar somewhere. Maybe the GCC
contains unbalanced quotes or parentheses?
next prev parent reply other threads:[~2002-10-10 20:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-10 11:43 Andreas Fuchs
2002-10-10 15:03 ` Simon Josefsson
2002-10-10 18:40 ` Andreas Fuchs
2002-10-10 20:23 ` Simon Josefsson [this message]
2002-10-10 20:58 ` Andreas Fuchs
2002-10-11 8:33 ` Kai Großjohann
2002-10-11 17:35 ` Andreas Fuchs
2002-10-11 17:38 ` Andreas Fuchs
2002-10-10 18:49 ` Paul Jarc
2002-10-10 19:35 ` Andreas Fuchs
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=ilun0pmdovm.fsf@h67n1c1o299.bredband.skanova.com \
--to=jas@extundo.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;
as well as URLs for NNTP newsgroup(s).