Thanx Trevor,

That's the way I have to do it, but sometimes one forgets....

Regards,
Kare

On Tue, 2007-05-08 at 09:44 +1200, Trevor Carey-Smith wrote:

> Hi,
> Not sure if this is the problem, but if your script is bailing out
> with an error before plend() is called then next time you run the
> script it will try to open plplot when its already open. There may be
> a better fix, but if you just call plend() before rerunning your
> script it might solve your problem
> 
> Regards,
> Trevor.
> 
> ----- Original Message -----
> From: Kåre Edvardsen <[EMAIL PROTECTED]>
> Date: Monday, May 7, 2007 10:57 pm
> Subject: [Perldl] More plplot issues...
> To: Perl <[email protected]>
> 
> > There is a very unfortunate thing with plplot and PDL; when making
> > mistakes which makes PDL barf, I often experience the whole PDL 
> > sessionto terminate with segmentation fault. If I for instance 
> > get a warning
> > like:
> > 
> > perldl> do 'test.pl'
> > Can't call method "nslice" on an undefined value at test.pl line
> 187.
> > 
> > I then correct the mistake and re-run the code, but somehow my
> plplot
> > calls are messed up, even they are correct programmed and I get this
> > error:
> > 
> > *** PLPLOT WARNING ***
> > plsdev: Must be called before plinit.
> > Segmentation fault
> > 
> > This is not very funny when it takes 15 min to re-run the whole 
> > chunk of
> > code which builds up the piddles I want to plot.
> > 
> > Does anyone know if Is it possible to make the perldl session more
> > crash-safe?
> > 
> > Cheers,
> > Kare
> > 

_______________________________________________
Perldl mailing list
[email protected]
http://mailman.jach.hawaii.edu/mailman/listinfo/perldl

Reply via email to