ports/162045: ghostview-1.5_2 coredumps on certain files

Ronald F.Guilmette rfg at tristatelogic.com
Thu Oct 27 01:40:09 UTC 2011


>Number:         162045
>Category:       ports
>Synopsis:       ghostview-1.5_2 coredumps on certain files
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Oct 27 01:40:08 UTC 2011
>Closed-Date:
>Last-Modified:
>Originator:     Ronald F. Guilmette
>Release:        FreeBSD 8.2-RELEASE amd64
>Organization:
>Environment:
System: FreeBSD coredump.tristatelogic.com 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Thu Feb 17 02:41:51 UTC 2011     root at mason.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  amd64

>Description:
	A certain valid Postscript file that I have in my possession is repeatedly causing
	ghostview to crash with a coredump at startup.  (I know the file is completely valid
	because when I just simply `cat' it to /def/ulpt0 it prints out beautifully and with
	no problems.)

	I'll provide the file upon request, but I would prefer not to publish it widely.

	The file in question is nothing special.  It was generated from a .pdf file by pdf2ps
	and it is just a three page business document.  No graphics, no multimedia, nothin'
	fancy.  Just straight text.

>How-To-Repeat:
	Run ghostscript on this file I have here (available upon request).

>Fix:
	I don't have any idea even how to debug this.  I did try compiling ghostscript with
	make -DWITH_DEBUG="yes" (as suggested in some places) and that allows me to get at
	least a stack traceback after the coredump, but gdb still isn't letting me do the
	"list" command (and I'm not even sure why) so I can't even find out which source line
	ghostview is crashing on.

	Here is the stack backtrace:

	(gdb) where
	#0  0x0000000000410fe7 in psscan ()
	#1  0x0000000000408687 in setup_ghostview ()
	#2  0x0000000000405d2a in main ()
	(gdb) 

	Should I be filing a bug report on GDB also?  I mean, you know, since the "list" command
	doesn't seem to work?
>Release-Note:
>Audit-Trail:
>Unformatted:



More information about the freebsd-ports-bugs mailing list