Bug#320627: crash w/ xpdf

["Nikita V. Youshchenko" <yoush@cs.msu.su>]

> #0  0x0fcf5c40 in kill () from /lib/libc.so.6
> No symbol table info available.
> #1  0x0fcf5a08 in raise () from /lib/libc.so.6
> No symbol table info available.
> #2  0x0fcf7140 in abort () from /lib/libc.so.6
> No symbol table info available.
> #3  0x1045ec7c in ddxGiveUp () at xf86Init.c:1264
>         i = 1
> #4  0x1045edfc in AbortDDX () at xf86Init.c:1319
>         i = 1
> #5  0x105907c0 in AbortServer () at log.c:395
> No locals.
> #6  0x10590cf8 in FatalError (
>     f=0x10ccb210 "Caught signal %d.  Server aborting\n") at log.c:541
>         args = {{gpr = 2 '\002', fpr = 0 '\0', reserved = 51740, 
>     overflow_arg_area = 0x7f8cc0b8, reg_save_area = 0x7f8cc028}}
>         beenhere = 1
> #7  0x104883b8 in xf86SigHandler (signo=11) at xf86Events.c:1294
> No locals.
> #8  <signal handler called>
> No symbol table info available.
> Cannot access memory at address 0x304

Looks like a stack breakage caused a segfault.

Maybe it would be useful to run same xpdf throurg X protocol monitor (xmon 
package), to see which request is causing the crash.