PDA

View Full Version : PV Wave on Debian Etch release



Juergen Salk
04-16-2007, 02:56 PM
Hi,

is there anybody out there, who is also running PV-Wave v8.51 on
Debian Etch release? Our PV-Wave based application has been
running successfully until Etch' mid-march version. However, PV-Wave
now segfaults when calling the `tv' procedure to display an image.

This is a screen capture when running the `tv' demo from
the PV-Wave documentation:

--- snip ---

WAVE> mandril = BYTARR(512, 512)
WAVE> OPENR, unit, !Data_dir + 'mandril.img', /Get_lun
WAVE> READU, unit, mandril
WAVE> WINDOW, XSize=512, YSize=512
WAVE> TV, mandril
% ERROR: Signal encountered: Segmentation violation.
% Since this may indicate a serious problem, it is recommended
% you save all data and restart PV-WAVE.
% Execution halted at $MAIN$ (TV).
WAVE>

--- snip ---

I suspect this segfault results from our latest upgrade to
the Debian Etch stable release, since the error did not happen
before (to my knowledge).
I would appreciate it, if someone, who has a PV-Wave installation
at his fingertips, would be willing to try to reproduce this
problem on latest Etch and share his findings with me (or even
better: with the forum).

Thanks in advance

Juergen

rwagner
04-16-2007, 04:05 PM
Hi Juergen,

I have an installation of PV-WAVE on a Debian system around here somewhere. I know it is not up to date, but in the next day or two I'll run a system update on it and run this demo. Please check back in a day or two for the results.

-Ryan

Juergen Salk
04-16-2007, 11:07 PM
Hi Ryan,

thanks for your reply. The problem described above seems to
be related to the latest libx11 upgrade to version 2:1.0.3-7 on
Debian Etch. This upgrade fixes some security issues in libx11.

This problem and a possible workaround has also been discussed
at the debian-science mailing list:

http://lists.debian.org/debian-science/2007/04/msg00014.html

Thanks again.

Best regards - Juergen

rwagner
04-19-2007, 08:46 AM
Hi Juergen,
My tests resulted in similar messages. I agree with your diagnosis that it is because of the libx11 upgrade to version 2:1.0.3-7.
-Ryan