Re: [Plplot-devel] Re: New way of getting device info from dyndrivers

[Rafael L. <lab...@ps...>]

* Alan W. Irwin <ir...@be...> [2003-02-10 10:25]:

> I don't completely trust such interpretation because I have seen segfaults
> come and go depending on the placement (!) of print statements in the code.
> It is very hard to track down the real reason for segfaults until you use a
> tool like valgrind.
> 
> valgrind does indicate a problem with xwin even when lt_dlclose is
> commented out. So I suggest the best test is to uncomment lt_dlclose and
> exclude both xwin and tkwin.  Under those circumstances, then I would
> believe the above interpretation (problem somewhere in either xwin or tkwin
> or both) if the valgrind result is clean. Otherwise not.

I understand your point and I agree that such bugs are hard to be tracked
down.  However, the simple fact that dlopening/dlclosing tkwin.la _with
everything else kept equal_ makes it a quite good candidate for culprit.
Indeed, there are tones of malloc, calloc, ckcalloc, etc calls in the source
files (drivers/tk*.c and bindings/tk/*.c).  I cannot tell if they are
suspicious or not, though.

That said, it is possible that the code in xwin.c is equally bad...

At any rate:

> I don't have time to run this specific test now, but I will do so in the
> next few days if nobody else is curious enough to try it.

we are looking forward for the results of your valgrind tests.

-- 
Rafael