[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #44292] Frequent crashes when printing to eps
From: |
Dan Sebald |
Subject: |
[Octave-bug-tracker] [bug #44292] Frequent crashes when printing to eps on Windows platform |
Date: |
Sat, 28 Feb 2015 09:49:13 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 SeaMonkey/2.15 |
Follow-up Comment #16, bug #44292 (project octave):
The changes with the new code
if (! file.empty () && file[0] == '|')
file = file.substr (1); // Strip leading pipe character
are more robust than previous. However, I can still get the following
behavior:
octave:1> surf (peaks)
octave:2> print -depsc tst.eps
pipeline =
{
[1,1] = /dev/null
}
error: drawnow: nonexistent directory ' | /dev/'
error: called from
__opengl_print__ at line 172 column 7
print at line 431 column 14
octave:2>
and
octave:1> surf (peaks)
octave:2> print -depsc tst.eps
sh: -c: line 0: syntax error near unexpected token `|'
sh: -c: line 0: ` |'
warning: broken pipe
pipeline =
{
[1,1] =
}
octave:2>
by massaging the pipeline whitespace. I know it is a contrived situation, but
still drawnow() is a user-callable function.
Also, I suspect that the current, recently added changes to
__osmesa_print__.cc could result in a segmentation fault if the string is
tweaked in the wrong way. However, I'm having problems with seg faults
elsewhere after building with the new OSMesa code--related to the osmesa
library being out of date probably (v. 7.9, but I can't compile the latest
10.2 OSMesa because it wants recent GLProto, which is getting into x11 files,
something I don't want to deal with now) and rend.draw() which is also
crashing, but I'm not sure why.
I've attached a patch that I think handles all situations of white space and
bogus file names in an organized way. Please try it and let me know how
OSMesa print is working for you. E.g.,
octave:1> surf (peaks)
octave:2> set (1, 'visible', 'off');
octave:3> print -depsc tst.eps
panic: Segmentation fault -- stopping myself...
attempting to save variables to 'octave-workspace'...
save to 'octave-workspace' complete
Segmentation fault (core dumped)
That seg fault is occurring before even reaching the changeset hunk.
(file #33209)
_______________________________________________________
Additional Item Attachment:
File name: octave-pipeline_decode-djs2015feb28.patch Size:3 KB
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?44292>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #44292] Frequent crashes when printing to eps on Windows platform, (continued)
- [Octave-bug-tracker] [bug #44292] Frequent crashes when printing to eps on Windows platform, John Donoghue, 2015/02/19
- [Octave-bug-tracker] [bug #44292] Frequent crashes when printing to eps on Windows platform, John Donoghue, 2015/02/19
- [Octave-bug-tracker] [bug #44292] Frequent crashes when printing to eps on Windows platform, Rik, 2015/02/20
- [Octave-bug-tracker] [bug #44292] Frequent crashes when printing to eps on Windows platform, Michael Godfrey, 2015/02/20
- [Octave-bug-tracker] [bug #44292] Frequent crashes when printing to eps on Windows platform, Rik, 2015/02/24
- [Octave-bug-tracker] [bug #44292] Frequent crashes when printing to eps on Windows platform, John Donoghue, 2015/02/24
- [Octave-bug-tracker] [bug #44292] Frequent crashes when printing to eps on Windows platform, Dan Sebald, 2015/02/26
- [Octave-bug-tracker] [bug #44292] Frequent crashes when printing to eps on Windows platform, Dan Sebald, 2015/02/26
- [Octave-bug-tracker] [bug #44292] Frequent crashes when printing to eps on Windows platform, Dan Sebald, 2015/02/26
- [Octave-bug-tracker] [bug #44292] Frequent crashes when printing to eps on Windows platform, Rik, 2015/02/27
- [Octave-bug-tracker] [bug #44292] Frequent crashes when printing to eps on Windows platform,
Dan Sebald <=