Re: Emacs aborts during byte-compilation from Dired

[David Kastrup]

Kenichi Handa <address@hidden> writes:

> In article <address@hidden>, Romain Francoise <address@hidden> writes:
>
> (gdb) watch ((struct Lisp_Symbol *) 0x838c8f8)->value
> Hardware watchpoint 4: ((struct Lisp_Symbol *) 137939192)->value
> (gdb) c
> Continuing.
>
> then, did this in Emacs:
>
>   M-x byte-compile-file RET ~/Fontifier.el RET
>
> then, Emacs stopped as below:
>
> Hardware watchpoint 4: ((struct Lisp_Symbol *) 137939192)->value
>
> Old value = 137939193
> New value = 144315101
> print_preprocess (obj=144315101) at print.c:1415
> (gdb) 
>
> The lines around print.c:1415 are:
>
>   1412                  /* If Vprint_continuous_numbering is non-nil and OBJ 
> is a gensym,
>   1413                     always print the gensym with a number.  This is a 
> special for
>   1414                     the lisp function byte-compile-output-docform.  */
>   1415                  if (!NILP (Vprint_continuous_numbering)
>   1416                      && SYMBOLP (obj)
>   1417                      && !SYMBOL_INTERNED_P (obj))
>   1418                    PRINT_NUMBER_STATUS (Vprint_number_table, 
> print_number_index) = Qt;
>   1419                  print_number_index++;
>
> I have no idea why the value of Qt is changed at L1415 (note
> that I compiled print.c without optimization).

Well, you'll get pointed to the IP after the hardware breakpoint
triggered.  So the interesting code would be before those comments.

-- 
David Kastrup