Re: 21.2.19 assert failure, editing in minibuf
>>>> "Jan" == Jan Vroonhof
<vroonhof(a)math.ethz.ch> writes:
Jan> Karl Kleinpaste <karl(a)justresearch.com> writes:
> I was editing a minibuf prompt, which had a default response that
I
> was altering. I had backed up to the first character in the minibuf,
> a comma, and hit M-BS a last time (after deleting several words
> beforehand) to eliminate it.
I just got a crash while editing in the minibuf, too. :-(
I was doing a filename completion, and had just pressed tab when the
crash occurred.
The back trace (shown in part below), is very similar to Karl's:
#0 0xef07452c in kill ()
#1 0xa0108 in fatal_error_signal (sig=6) at emacs.c:276
#2 <signal handler called>
#3 0xef07452c in kill ()
#4 0xef03a5d4 in abort ()
#5 0xa3584 in assert_failed (file=0x30d520 "insdel.c", line=607,
expr=0x30d5d8 "( newmin) > BI_BUF_BEG (buf) && newmin <= BI_BUF_Z
(buf)") at emacs.c:2672
#6 0x18e6dc in bufpos_to_bytind_func (buf=0x430c00, x=0) at insdel.c:607
#7 0x18f364 in bufpos_to_bytind (buf=0x430c00, x=0) at buffer.h:986
#8 0x2249fc in scan_words (buf=0x430c00, from=1, count=-1) at syntax.c:427
#9 0x224e40 in Fforward_word (count=-1, buffer=4393984) at syntax.c:476
#10 0x69e6c in execute_rare_opcode (stack_ptr=0xefffc1fc,
program_ptr=0x110656a
"\210`\026\a\016\nfzËU«\013\016\nb\210Ìv\210`\026\n\016\016b\210\016\r\016\a\016\nZX\020\016\a\016\nZ\016\017X\006\016\n\016\a{)\207\001",
opcode=Bforward_word)
at bytecode.c:1390
#11 0x68b6c in execute_optimized_program (program=0xefffc1fc "ÿÿÿÿ",
stack_depth=118,
constants_data=0x1551b10) at bytecode.c:657
#12 0x685f4 in funcall_compiled_function (fun=24612332, nargs=0, args=0xefffc458) at
bytecode.c:523
#13 0xacfac in Ffuncall (nargs=0, args=0xefffc454) at eval.c:3221
#14 0x68ebc in execute_optimized_program (program=0xefffc454 "\001Vª€",
stack_depth=0,
constants_data=0x13fb090) at bytecode.c:747
#15 0x685f4 in funcall_compiled_function (fun=24612360, nargs=0, args=0xefffc6a8) at
bytecode.c:523
#16 0xacfac in Ffuncall (nargs=0, args=0xefffc6a4) at eval.c:3221
#17 0x68ebc in execute_optimized_program (program=0xefffc6a4 "\001VªŒ",
stack_depth=0,
constants_data=0x13fb6d0) at bytecode.c:747
#18 0x685f4 in funcall_compiled_function (fun=24742536, nargs=0, args=0xefffc900) at
bytecode.c:523
#19 0xacfac in Ffuncall (nargs=0, args=0xefffc8fc) at eval.c:3221
#20 0x68ebc in execute_optimized_program (program=0xefffc8fc
"\001V£L\001V\231\fï\035Åž",
stack_depth=0, constants_data=0x1799490) at bytecode.c:747
#21 0x685f4 in funcall_compiled_function (fun=24743292, nargs=0, args=0xefffcc54) at
bytecode.c:523
#22 0xacfac in Ffuncall (nargs=0, args=0xefffcc50) at eval.c:3221
#23 0xae37c in run_hook_with_args_in_buffer (buf=0x3dc804, nargs=1, args=0xefffcc50,
cond=RUN_HOOKS_TO_COMPLETION) at eval.c:3671
Jan> Did this prompt have any high-bit characters in it?
Not for me.
Jan> It _is_ crashing in a new part of the code. However the assert is
Jan> close to impossible to trigger. So this crash is very weird.
Jan> Do you still have the core file?
Yes.
> #4 0x81360f3 in bufpos_to_bytind_func (buf=0x8318ee8, x=0) at
insdel.c:607
Jan> Could you check buf->pt and buf->bufpt in this frame? (As well as the
Jan> value of bufmin).
#6 0x18e6dc in bufpos_to_bytind_func (buf=0x430c00, x=0) at insdel.c:607
607 DEC_BYTIND (buf, newmin);
(gdb) p buf
$1 = (struct buffer *) 0x430c00
(gdb) p buf->pt
$2 = 8
(gdb) p buf->bufpt
$3 = 8
Jan> Which gcc version do you use?
2.7.2.2 on Solaris 2.5.1.
If you need more info, I can give it to you.
Ray