Re: SIGSEGV in X export display.

[Richard Stallman]

    Program received signal SIGSEGV, Segmentation fault.
    [Switching to Thread 16384 (LWP 19690)]
    0x0817ef1d in mark_object (arg=3D135891787) at alloc.c:5509
    5509            MARK_INTERVAL_TREE (ptr->intervals);

I did not realize that there was a SEGV inside mark_object.  That is
very important.  It probably means that something created invalid a
Lisp object, and later GC stumbled across it.

    #0  0x0817ef1d in mark_object (arg=3D135891787) at alloc.c:5509
            ptr =3D (struct Lisp_String *) 0x8198b48
            obj =3D 135891787
            cdr_count =3D 0
    #1  0x081cd803 in mark_byte_stack () at bytecode.c:294
            stack =3D (struct byte_stack *) 0xbf81c210
            obj =3D (Lisp_Object *) 0xbf81c288

The next step is to find out which stack slot is being marked,
and then find out what that stack slot really is.
Which stack frame is it in; what variable is it?