[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #55647] crash, hang, error or corrupted output

From: Pantxo Diribarne
Subject: [Octave-bug-tracker] [bug #55647] crash, hang, error or corrupted output when printing some demos to EPS
Date: Wed, 6 Feb 2019 14:44:21 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:64.0) Gecko/20100101 Firefox/64.0

Update of bug #55647 (project octave):

                  Status:                    None => Confirmed              


Follow-up Comment #4:

@Rik: Yes the problem is present in default and may have been there for a
while: before Octave 5, the default was "-loose" so we did not use epstool and
probably just didn't notice the misbehavior.

@Dmitri: epstool is ran through a pipe which is fed directly with the original
gl2ps-generated EPS output. Then when closing the pipe, fclose only returns
when epstool has finished. So I am pretty sure there cannot be a race
condition here.

Now about the second issue, the bad bbox when using "-loose", can one of you
reproduce it? Actually I am only able to trigger it on my most recent system
(linux Mint 19.1, whith Ghostscript 9.26 among others). On debian stretch the
bbox is OK after

demo hold 6
axis auto
print -loose -depsc toto.eps


Reply to this item at:


  Message posté via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]