From: Paul Stodghill <stodghil@cs.cornell.edu>
Subject: fill bug still there [Re: XEmacs 21.[45] + Oort Gnus 0.03 + Filladapt 2.12: Inf loop]
Date: 28 May 2001 13:45:10 -0400 [thread overview]
Message-ID: <yz1d78t1ixo.fsf@milhouse.cs.cornell.edu> (raw)
In-Reply-To: <yz1r8xi1qi3.fsf@milhouse.cs.cornell.edu> (Paul Stodghill's message of "21 May 2001 15:14:03 -0400")
The XEmacs people have made the changes so that C-g breaks out of the
infloop that happens as I have described in previous messages.
However, I never heard from any of the Gnus developers about what is
causing the infloop in the first place. Below is a backtrace that I was
able to obtain by killing an infloop'ing XEmacs.
I can't isolate the particular piece of code that is causing this bug.
Could people who know more than I please look at this.
Thank you.
> I managed to get a backtrace by sending HUP to a xemacs-21.5-b1 process
> that was in an infloop. Here it is,
>
> milhouse$ xemacs-21.5-b1
>
> [1]+ Stopped xemacs-21.5-b1
> milhouse$ bg
> [1]+ xemacs-21.5-b1 &
> milhouse$ kill -1 %1
> milhouse$
> Fatal error (1).
>
> Your files have been auto-saved.
> Use `M-x recover-session' to recover them.
>
> If you have access to the PROBLEMS file that came with your
> version of XEmacs, please check to see if your crash is described
> there, as there may be a workaround available.
> Otherwise, please report this bug by running the send-pr
> script included with XEmacs, or selecting `Send Bug Report'
> from the help menu.
> As a last resort send ordinary email to `crashes@xemacs.org'.
> *MAKE SURE* to include the information in the command
> M-x describe-installation.
>
> If at all possible, *please* try to obtain a C stack backtrace;
> it will help us immensely in determining what went wrong.
> To do this, locate the core file that was produced as a result
> of this crash (it's usually called `core' and is located in the
> directory in which you started the editor, or maybe in your home
> directory), and type
>
> gdb /usr/local/bin/xemacs-21.5-b1.exe core
>
> then type `where' when the debugger prompt comes up.
> (If you don't have GDB on your system, you might have DBX,
> or XDB, or SDB. A similar procedure should work for all of
> these. Ask your system administrator if you need more help.)
>
> Lisp backtrace follows:
>
> looking-at("--text follows this line--$\\|[ ]*$\\|-- $\\|---+$\\|^?$\\|.*wro
> te:$\\|\\(\\([ ]*\\(\\w\\|[-_.]\\)+>+\\|[ ]*[]>>|:}+]\\)+\\)[ ]*$")
> # bind (quoted point beg end leading-space bolp not-break arg)
> message-newline-and-reformat(nil t)
> # bind (arg)
> message-fill-paragraph(nil)
> # bind (function fill-paragraph-function arg)
> #<compiled-function (arg) "...(54)" [function before end start arg fill-paragr
> aph-function nil forward-paragraph newline 1 backward-paragraph fill-region fill
> -region-as-paragraph use-hard-newlines] 5 1025528 (list (if current-prefix-arg .
> ..))>(nil)
> apply(#<compiled-function (arg) "...(54)" [function before end start arg fill-
> paragraph-function nil forward-paragraph newline 1 backward-paragraph fill-regio
> n fill-region-as-paragraph use-hard-newlines] 5 1025528 (list (if current-prefix
> -arg ...))> nil)
> # bind (args function)
> filladapt-funcall(fill-paragraph nil)
> # bind (paragraph-ignore-fill-prefix adaptive-fill-mode adaptive-fill-regexp c
> omment-multi-line fill-prefix retval)
> # (unwind-protect ...)
> byte-code("..." [function done retval sign delta fill-column nil t filladapt-a
> dapt 1 0 filladapt-funcall filladapt-paragraph-within-fill-tolerance success run
> -hooks filladapt-fill-paragraph-post-hook throw arg low high lim fill-prefix old
> -fill-column filladapt-mode comment-multi-line adaptive-fill-regexp adaptive-fil
> l-mode paragraph-ignore-fill-prefix filladapt-fill-column-tolerance filladapt-fi
> ll-column-backward-fuzz filladapt-fill-column-forward-fuzz] 7)
> # (catch done ...)
> # bind (arg function)
> filladapt-fill-paragraph(fill-paragraph nil)
> # bind (filladapt-inside-filladapt arg)
> fill-paragraph(nil)
> # bind (command-debug-status)
> call-interactively(fill-paragraph)
> # bind (arg)
> fill-paragraph-or-region(nil)
> # bind (command-debug-status)
> call-interactively(fill-paragraph-or-region)
> # (condition-case ... . error)
> # (catch top-level ...)
next prev parent reply other threads:[~2001-05-28 17:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-21 13:50 XEmacs 21.[45] + Oort Gnus 0.03 + Filladapt 2.12: Inf loop Paul Stodghill
2001-05-21 14:09 ` Hrvoje Niksic
2001-05-21 14:37 ` Josh Huber
2001-05-21 15:05 ` Olivier Fambon
2001-05-21 15:15 ` Paul Stodghill
2001-05-21 16:07 ` Andy Piper
2001-05-21 19:13 ` Paul Stodghill
2001-05-21 19:14 ` Paul Stodghill
2001-05-28 17:45 ` Paul Stodghill [this message]
2001-05-29 17:20 ` fill bug still there [Re: XEmacs 21.[45] + Oort Gnus 0.03 + Filladapt 2.12: Inf loop] Simon Josefsson
2001-05-29 17:24 ` Paul Stodghill
2001-05-29 17:22 ` Kai Großjohann
2001-05-29 17:26 ` Paul Stodghill
2001-05-29 17:50 ` Kai Großjohann
2001-05-29 17:56 ` Paul Stodghill
2001-05-27 3:38 ` critical quit Re: XEmacs 21.[45] + Oort Gnus 0.03 + Filladapt 2.12: Inf loop Ben Wing
2001-05-28 17:44 ` Paul Stodghill
2001-05-30 1:28 ` Ben Wing
2001-05-30 7:08 ` Wow Ken McGlothlen
2001-05-30 9:26 ` Wow Kai Großjohann
2001-05-30 21:19 ` Wow Ken McGlothlen
2001-05-30 21:26 ` Wow Kai Großjohann
2001-05-31 9:10 ` Wow Steinar Bang
2001-06-01 21:30 ` Wow Ken McGlothlen
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=yz1d78t1ixo.fsf@milhouse.cs.cornell.edu \
--to=stodghil@cs.cornell.edu \
/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).