Bug 88842 - dvipdfm segfaults
dvipdfm segfaults
Product: Red Hat Raw Hide
Classification: Retired
Component: tetex (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Waugh
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2003-04-14 15:56 EDT by Sammy
Modified: 2007-04-18 12:53 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-04-24 10:23:35 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Small TeX file with figure (7.18 KB, text/plain)
2003-04-15 10:53 EDT, Sammy
no flags Details
Included eps file (1.24 KB, text/plain)
2003-04-15 10:54 EDT, Sammy
no flags Details
New patch file (730 bytes, patch)
2003-04-15 14:28 EDT, Sammy
no flags Details | Diff

  None (edit)
Description Sammy 2003-04-14 15:56:16 EDT
The executable dvipdfm (which is used by kdvi from kegraphics package) 
segfaults when run on a dvi file containing embedded eps figures. It runs 
ok when the document contains no figures. I am at the latest rawhide level 
as of 4-14-2003.
Comment 1 Sammy 2003-04-15 10:53:38 EDT
Created attachment 91141 [details]
Small TeX file with figure
Comment 2 Sammy 2003-04-15 10:54:40 EDT
Created attachment 91142 [details]
Included eps file

Any eps file would do!
Comment 3 Sammy 2003-04-15 11:59:11 EDT
I have built the dvipdfm-0.13.2c-1.i386.rpm from its source and installed 
it over tetex and this one does not crash with any eps file. I could not 
figure out though what the difference is between the two. 
Comment 4 Sammy 2003-04-15 14:27:30 EDT
The culprit seems to be tetex-2.0.2-dvipdfm-security.patch. I am not an expert in 
mkstemp but looking at other examples made a new patch, which does not segfault. 
This is attached below. 
Comment 5 Sammy 2003-04-15 14:28:12 EDT
Created attachment 91145 [details]
New patch file
Comment 6 Tim Waugh 2003-04-24 10:23:35 EDT
Next build will contain the fix.  Thanks.

Note You need to log in before you can comment on or make changes to this bug.