[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #45348] print file.eps or any other suffix cau
From: |
Michael Godfrey |
Subject: |
[Octave-bug-tracker] [bug #45348] print file.eps or any other suffix causes mesa abort with Intel HD6000 drivers |
Date: |
Tue, 13 Oct 2015 23:48:44 +0000 |
User-agent: |
Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/47.0.2526.8 Safari/537.36 |
Follow-up Comment #5, bug #45348 (project octave):
I noticed that the new mesa libs produce a different
dump from before:
++vebatim++
>> print zzz.pdf
panic: Segmentation fault -- stopping myself...
attempting to save variables to 'octave-workspace'...
save to 'octave-workspace' complete
Error: /syntaxerror in -file-
Operand stack:
STnoshfill
Execution stack:
%interp_exit .runexec2 --nostringval-- --nostringval--
--nostringval-- 2 %stopped_push --nostringval-- --nostringval--
--nostringval-- false 1 %stopped_push 1951 1 3 %oparray_pop
1950 1 3 %oparray_pop --nostringval-- 1934 1 3 %oparray_pop
1820 1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2
--nostringval-- --nostringval-- --nostringval-- 2 %stopped_push
Dictionary stack:
-Segmentation fault (core dumped)
-dict:1192/1684(ro)(G)-- --dict:0/20(G)-- --dict:83/200(L)--
--dict:37/64(L)--
Current allocation mode is local
Last OS error: Not a directory
GPL Ghostscript 9.16: Unrecoverable error, exit code 1
__verbatim__
Notice the STnoshfill at the top of the dump.
This is a symbol defined in Binary file /usr/lib64/./libgl2ps.so.1.3.8
This suggests that it is a call to gl2ps that causes the seg fault.
This is not all that helpful, but it may suggest something to whoever
knows how gl2ps is used in the print process.
Tell me if a full bt would be helpful.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?45348>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/