* RMAIL causes Emacs abort
@ 2003-08-12 14:58 Robert J. Chassell
2003-08-12 20:25 ` Paul Michael Reilly
0 siblings, 1 reply; 2+ messages in thread
From: Robert J. Chassell @ 2003-08-12 14:58 UTC (permalink / raw)
Today's CVS snapshot, Tue, 2003 Aug 12 14:28 UTC
GNU Emacs 21.3.50.33 (i686-pc-linux-gnu, X toolkit)
started with
/usr/local/bin/emacs -q --no-site-file --eval '(blink-cursor-mode 0)'
When both /var/mail/bob and ~/RMAIL are zero length files,
the command
M-x rmail
causes Emacs to abort. The same occurs when either /var/mail/bob or
~/RMAIL have content.
However, when /var/mail/bob is a zero length file,
when a full ~/RMAIL is first found with `M-x find-file-literally' and
when rmail is run with a prefix command, `C-u M-x rmail'
then Emacs does not abort and I can read my RMAIL.
Here is the GDB backtrace from the first situation,
starting Emacs with both /var/mail/bob and ~/RMAIL as zero length files.
The command was `M-x rmail':
Program received signal SIGABRT, Aborted.
0x402eea51 in kill () from /lib/libc.so.6
Argument list to give program being debugged when it is started is
"-q --no-site-file --eval '(blink-cursor-mode 0)'".
(gdb) bt
#0 0x402eea51 in kill () from /lib/libc.so.6
#1 0x080d55c2 in abort () at emacs.c:417
#2 0x0811fab3 in wrong_type_argument (predicate=405614116, value=31625)
at data.c:120
#3 0x0811c7a1 in Fmake_vector (length=-1, init=405499604) at alloc.c:2622
#4 0x0811c8c7 in Fvector (nargs=-1, args=0xbfffe810) at alloc.c:2681
#5 0x0809a1ea in coding_restore_composition (coding=0x0, obj=1214733304)
at coding.c:5451
#6 0x0809a963 in code_convert_region (from=1985638, from_byte=2055935,
to=1994938, to_byte=2065235, coding=0xbfffe950, encodep=0, replace=1)
at coding.c:5924
#7 0x0809ce99 in code_convert_region1 (start=1985638, end=1994938,
coding_system=140991480, encodep=0) at coding.c:6902
#8 0x0809cf66 in Fdecode_coding_region (start=1985638, end=1994938,
coding_system=405683620) at coding.c:6920
#9 0x08131556 in Ffuncall (nargs=4, args=0xbfffeca4) at eval.c:2724
#10 0x08158e7d in Fbyte_code (bytestr=405634132, vector=3,
maxdepth=-1073746784) at bytecode.c:710
#11 0x08131864 in funcall_lambda (fun=1214680080, nargs=3,
arg_vector=0xbfffedb4) at eval.c:2911
#12 0x0813142f in Ffuncall (nargs=4, args=0xbfffedb0) at eval.c:2781
#13 0x08158e7d in Fbyte_code (bytestr=405655020, vector=3,
maxdepth=-1073746512) at bytecode.c:710
#14 0x08131864 in funcall_lambda (fun=1214688952, nargs=0,
arg_vector=0xbfffeee4) at eval.c:2911
#15 0x0813142f in Ffuncall (nargs=1, args=0xbfffeee0) at eval.c:2781
#16 0x08158e7d in Fbyte_code (bytestr=1481008896, vector=0,
maxdepth=-1073746208) at bytecode.c:710
#17 0x08131864 in funcall_lambda (fun=1214679272, nargs=0,
arg_vector=0xbffff014) at eval.c:2911
#18 0x0813142f in Ffuncall (nargs=1, args=0xbffff010) at eval.c:2781
#19 0x08158e7d in Fbyte_code (bytestr=408468500, vector=0,
maxdepth=-1073745904) at bytecode.c:710
#20 0x08131864 in funcall_lambda (fun=1213776720, nargs=0,
arg_vector=0xbffff144) at eval.c:2911
#21 0x0813142f in Ffuncall (nargs=1, args=0xbffff140) at eval.c:2781
#22 0x08131236 in apply1 (fn=406264100, arg=405499604) at eval.c:2476
#23 0x0812df34 in Fcall_interactively (function=406264100,
record_flag=405499652, keys=1210880224) at callint.c:399
#24 0x080e2b8e in Fcommand_execute (cmd=406264100, record_flag=405499652,
keys=405499604, special=405499604) at keyboard.c:9724
#25 0x080e2e8e in Fexecute_extended_command (prefixarg=405499604)
at keyboard.c:9835
#26 0x08131556 in Ffuncall (nargs=2, args=0xbffff434) at eval.c:2724
#27 0x0812d402 in Fcall_interactively (function=405607124,
record_flag=405499604, keys=1210880224) at callint.c:850
#28 0x080e2b8e in Fcommand_execute (cmd=405607124, record_flag=405499604,
keys=405499604, special=405499604) at keyboard.c:9724
#29 0x080d81cb in command_loop_1 () at keyboard.c:1755
#30 0x0812fa6a in internal_condition_case (bfun=0x80d7e74 <command_loop_1>,
handlers=405610716, hfun=0x80d7a68 <cmd_error>) at eval.c:1333
#31 0x080d7d4a in command_loop_2 () at keyboard.c:1292
#32 0x0812f609 in internal_catch (tag=0, func=0x80d7d2c <command_loop_2>,
arg=405499604) at eval.c:1094
#33 0x080d7d00 in command_loop () at keyboard.c:1271
#34 0x080d7844 in recursive_edit_1 () at keyboard.c:987
#35 0x080d7954 in Frecursive_edit () at keyboard.c:1043
#36 0x080d62b5 in main (argc=5, argv=0xbffffbd4) at emacs.c:1666
(gdb)
--
Robert J. Chassell Rattlesnake Enterprises
http://www.rattlesnake.com GnuPG Key ID: 004B4AC8
http://www.teak.cc bob@rattlesnake.com
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: RMAIL causes Emacs abort
2003-08-12 14:58 RMAIL causes Emacs abort Robert J. Chassell
@ 2003-08-12 20:25 ` Paul Michael Reilly
0 siblings, 0 replies; 2+ messages in thread
From: Paul Michael Reilly @ 2003-08-12 20:25 UTC (permalink / raw)
Cc: emacs-devel
Robert J. Chassell wrote:
>Today's CVS snapshot, Tue, 2003 Aug 12 14:28 UTC
>GNU Emacs 21.3.50.33 (i686-pc-linux-gnu, X toolkit)
>started with
>
> /usr/local/bin/emacs -q --no-site-file --eval '(blink-cursor-mode 0)'
>
>When both /var/mail/bob and ~/RMAIL are zero length files,
>the command
>
> M-x rmail
>
>causes Emacs to abort. The same occurs when either /var/mail/bob or
>~/RMAIL have content.
>
>However, when /var/mail/bob is a zero length file,
> when a full ~/RMAIL is first found with `M-x find-file-literally' and
> when rmail is run with a prefix command, `C-u M-x rmail'
> then Emacs does not abort and I can read my RMAIL.
>
>Here is the GDB backtrace from the first situation,
>starting Emacs with both /var/mail/bob and ~/RMAIL as zero length files.
>The command was `M-x rmail':
>
>
...
I will take a look at this problem.
-pmr
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2003-08-12 20:25 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-08-12 14:58 RMAIL causes Emacs abort Robert J. Chassell
2003-08-12 20:25 ` Paul Michael Reilly
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).