[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #53010] SIGABRT while using print command with
From: |
Rik |
Subject: |
[Octave-bug-tracker] [bug #53010] SIGABRT while using print command with unknown printer |
Date: |
Tue, 30 Jan 2018 12:53:36 -0500 (EST) |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0 |
Update of bug #53010 (project octave):
Category: Octave Function => Plotting with OpenGL
Status: None => Confirmed
_______________________________________________________
Follow-up Comment #1:
Confirmed. Changing the category to Plotting with OpenGL, although it is
really only an issue with the qt toolkit.
The issue is a familiar one in that when using the qt toolkit there can be
multiple threads and when an error occurs during the print process the wrong
thread (i.e, one that does not have a signal handler installed) receives the
exception. Without an installed signal handler it calls the default which is
std::terminate.
When running with the FLTK toolkit, for example, I get
print -dpswrite -PXX
/usr/bin/lpr: The printer or class does not exist.
./base/gsicc_manage.c:1088: gsicc_open_search(): Could not find
default_gray.icc
| ./base/gsicc_manage.c:1708: gsicc_set_device_profile(): cannot find device
profile
error: gl2ps_renderer::draw: internal pipe error
error: called from
__opengl_print__ at line 155 column 7
print at line 552 column 14
The warnings in gsicc_manage.c are not material. The important thing is that
the gl2ps_renderer is calling the error() function which then then leads to
std::terminate.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?53010>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/