Raymond Toy <toy(a)rtp.ericsson.se> writes:
I had just done 'C-x C-h C-u M-| gindent" to have GNU indent
indent my
buffer and replace the buffer with the output of indent.
After the progress bar went away, XEmacs decided to GC, the GC cursor
popped up, and boom.
Could there be a GC bug in file_truename or some process I/O stuff?
Lately, whenever I get a crash in GC, it seems to be always just after
I've tried to do some kind of I/O like saving the file or auto-saving
the file.
Personally my guess would be that this is related to clash detection,
which seemed to be involved in a number of (your) crashes recently.
Ben fixed a lot of GC bugs in filelock.c, but maybe there are some left...
How do I go about tracking this down?
no idea. I've tried enabling always_gc in lock_file() but that hasn't
yielded any crashes so far.
Gunnar