From: "Robert J. Chassell" <bob@rattlesnake.com>
Subject: Re: Invisible colons in Emacs Info.
Date: Sat, 5 Jul 2003 14:28:59 -0400 (EDT) [thread overview]
Message-ID: <m19YrmN-000IeGC@rattlesnake.com> (raw)
In-Reply-To: <200307050314.h653ESE05056@raven.dms.auburn.edu> (message from Luc Teirlinck on Fri, 4 Jul 2003 22:14:28 -0500 (CDT))
Luc Teirlinck <teirllm@dms.auburn.edu> wrote:
... Info rather easily seems to go into infinite loops, with C-g
being of no help. ...
Example:
emacs-21.3.50 -q --eval "(blink-cursor-mode 0)" &
I can confirm this using
Today's CVS snapshot, Sat, 2003 Jul 5 18:18 UTC
GNU Emacs 21.3.50.117 (i686-pc-linux-gnu, X toolkit)
Here is a backtrace:
(gdb) bt
#0 0x081186be in re_match_2_internal (bufp=0x82aec9c, string1=0x0, size1=0,
string2=0x40411582 "File: info, Node: Top, Next: Getting Started, Up: (dir)\n\nInfo: An Introduction\n", '*' <repeats 21 times>, "\n\nThe GNU Project distributes most of its on-line manuals in the \"Info\nformat\", which you read us"..., size2=857, pos=586, regs=0x81c3fa4, stop=234) at regex.c:5559
#1 0x08116864 in re_search_2 (bufp=0x82aec9c,
str1=0x40411582 "File: info, Node: Top, Next: Getting Started, Up: (dir)\n\nInfo: An Introduction\n", '*' <repeats 21 times>, "\n\nThe GNU Project distributes most of its on-line manuals in the \"Info\nformat\", which you read us"..., size1=857, str2=0x40420ce2 "", size2=0, startpos=586, range=271,
regs=0x81c3fa4, stop=857) at regex.c:4262
#2 0x0810d7b3 in search_buffer (string=-58471, pos=1987, pos_byte=584,
lim=2260, lim_byte=2260, n=1, RE=1, trt=1212420280,
inverse_trt=1212441200, posix=0) at search.c:1103
#3 0x0810d0ad in search_command (string=946626620, bound=405492404,
noerror=405492452, count=140045003, direction=1, RE=1, posix=0)
at search.c:904
#4 0x0810f3a1 in Fre_search_forward (regexp=946626620, bound=405492404,
noerror=405492452, count=405492404) at search.c:2125
#5 0x08131556 in Ffuncall (nargs=4, args=0xbfffeba0) at eval.c:2724
#6 0x08158e91 in Fbyte_code (bytestr=-1073746928, vector=3,
maxdepth=-1073746928) at bytecode.c:710
#7 0x08131864 in funcall_lambda (fun=1213612088, nargs=0,
arg_vector=0xbfffed34) at eval.c:2911
#8 0x0813142f in Ffuncall (nargs=1, args=0xbfffed30) at eval.c:2781
#9 0x08158e91 in Fbyte_code (bytestr=408418124, vector=0,
maxdepth=-1073746640) at bytecode.c:710
#10 0x08131864 in funcall_lambda (fun=1213280688, nargs=0,
arg_vector=0xbfffee54) at eval.c:2911
#11 0x0813142f in Ffuncall (nargs=1, args=0xbfffee50) at eval.c:2781
#12 0x08158e91 in Fbyte_code (bytestr=407516436, vector=0,
maxdepth=-1073746352) at bytecode.c:710
#13 0x08131864 in funcall_lambda (fun=1212903736, nargs=3,
arg_vector=0xbfffef74) at eval.c:2911
#14 0x0813142f in Ffuncall (nargs=4, args=0xbfffef70) at eval.c:2781
#15 0x08158e91 in Fbyte_code (bytestr=407516460, vector=3,
maxdepth=-1073746064) at bytecode.c:710
#16 0x08131864 in funcall_lambda (fun=1212256064, nargs=2,
arg_vector=0xbffff094) at eval.c:2911
#17 0x0813142f in Ffuncall (nargs=3, args=0xbffff090) at eval.c:2781
#18 0x08158e91 in Fbyte_code (bytestr=407516436, vector=2,
maxdepth=-1073745776) at bytecode.c:710
#19 0x08131864 in funcall_lambda (fun=1212933496, nargs=2,
arg_vector=0xbffff1b4) at eval.c:2911
#20 0x0813142f in Ffuncall (nargs=3, args=0xbffff1b0) at eval.c:2781
#21 0x08158e91 in Fbyte_code (bytestr=408321860, vector=2,
maxdepth=-1073745488) at bytecode.c:710
#22 0x08131864 in funcall_lambda (fun=1212876272, nargs=2,
arg_vector=0xbffff2c4) at eval.c:2911
#23 0x0813142f in Ffuncall (nargs=3, args=0xbffff2c0) at eval.c:2781
#24 0x08130e5d in Fapply (nargs=2, args=0xbffff340) at eval.c:2231
#25 0x08131225 in apply1 (fn=408211020, arg=1483482500) at eval.c:2487
#26 0x0812df34 in Fcall_interactively (function=408211020,
record_flag=405492404, keys=1210874048) at callint.c:399
#27 0x080e2976 in Fcommand_execute (cmd=408211020, record_flag=405492404,
keys=405492404, special=405492404) at keyboard.c:9724
#28 0x080d7fb3 in command_loop_1 () at keyboard.c:1755
#29 0x0812fa6a in internal_condition_case (bfun=0x80d7c5c <command_loop_1>,
handlers=405604540, hfun=0x80d7850 <cmd_error>) at eval.c:1333
#30 0x080d7b32 in command_loop_2 () at keyboard.c:1292
#31 0x0812f609 in internal_catch (tag=86, func=0x80d7b14 <command_loop_2>,
arg=405492404) at eval.c:1094
#32 0x080d7ae8 in command_loop () at keyboard.c:1271
#33 0x080d762c in recursive_edit_1 () at keyboard.c:987
#34 0x080d773c in Frecursive_edit () at keyboard.c:1043
#35 0x080d609d in main (argc=4, argv=0xbffffae4) at emacs.c:1666
next prev parent reply other threads:[~2003-07-05 18:28 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-01 0:03 Invisible colons in Emacs Info Karl Berry
2003-07-01 0:31 ` Luc Teirlinck
2003-07-04 0:12 ` Stefan Monnier
2003-07-05 3:14 ` Luc Teirlinck
2003-07-05 18:28 ` Robert J. Chassell [this message]
2003-07-06 13:49 ` Kim F. Storm
2003-07-06 13:03 ` Robert J. Chassell
2003-07-06 18:17 ` Luc Teirlinck
2003-07-06 18:27 ` Luc Teirlinck
2003-07-06 19:19 ` Luc Teirlinck
2003-07-06 23:38 ` Kim F. Storm
2003-07-05 13:15 ` Luc Teirlinck
-- strict thread matches above, loose matches on Subject: below --
2003-07-06 23:56 Karl Berry
2003-07-07 0:47 ` Luc Teirlinck
2003-07-06 22:43 Karl Berry
2003-07-06 22:58 ` Luc Teirlinck
2003-07-06 23:07 ` Stefan Monnier
2003-07-06 23:42 ` Luc Teirlinck
2003-07-07 14:47 ` Stefan Monnier
2003-07-08 2:17 ` Luc Teirlinck
2003-06-25 21:04 Karl Berry
2003-06-25 20:00 Karl Berry
2003-06-25 19:58 Karl Berry
2003-06-25 20:12 ` Luc Teirlinck
2003-06-25 2:34 Luc Teirlinck
2003-06-25 2:45 ` Luc Teirlinck
2003-06-25 17:52 ` Stefan Monnier
2003-06-25 18:49 ` Luc Teirlinck
2003-06-25 18:56 ` Stefan Monnier
2003-06-25 18:59 ` Luc Teirlinck
2003-06-25 19:04 ` Luc Teirlinck
2003-06-25 19:13 ` Luc Teirlinck
2003-06-25 19:25 ` Luc Teirlinck
2003-06-25 19:58 ` Luc Teirlinck
2003-06-25 21:12 ` Stefan Monnier
2003-06-25 21:26 ` Luc Teirlinck
2003-06-28 0:36 ` Luc Teirlinck
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m19YrmN-000IeGC@rattlesnake.com \
--to=bob@rattlesnake.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).