* Sergio Gelato <[EMAIL PROTECTED]> [070719 19:26]:
> * Bernhard R. Link [2007-07-19 16:09:21 +0200]:
> > Can you still see this bug? Could you send a backtrace where the write
> > you speak about is called?
>
> Yes, I can reproduce the bug under sarge with the 3.6.1-10sarge2 version.
> I can't reproduce the crash under etch. (There is only a milder problem,
> that gv and evince --- but NOT gs -sDEVICE=x11 --- fail to display most
> of the text on that page; but that may only signal a bug in that PostScript
> file, most probably in the figure on that page.)
My etch gv seems to show everything on that page. I'm assuming this is
still the same problem though a milder incarnation as in sarge. What
does gs on etch with the options for antialiasing show?
> I now see (from strace output) that gs dies with SIGSEGV just before its
> parent gv receives the SIGPIPE. Running gs under gdb, then, with the
> same arguments gv is using (-sDEVICE=x11 -dTextAlphaBits=4
> -dGraphicsAlphaBits=2 -dMaxBitmap=10000000 -dNOPLATFONTS -dNOPAUSE
> -dQUIET -dSAFER) results in:
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x080d7aa3 in jpeg_mem_term ()
This very much looks like the cause and like a bug in gs-gpl, thus I've
just reassigned this bug to the gs-gpl package.
Hochachtungsvoll,
Bernhard R. Link
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
