Re: [Plplot-devel] valgrind tests on the python examples and also on C examples with -dev xwin

[Andrew R. <and...@us...>]

On Sat, Oct 16, 2004 at 05:37:19PM -0700, Alan Irwin wrote:
> On 2004-10-16 14:02-0500 mj...@ga... wrote:
> 
> >XOpenDisplay() does appear to be the first call, in the X driver at least
> >(except for XInitThreads, but that's a special case).  I'm not sure if 
> >there's
> >any absolute requirement that XOpenDisplay() come first -- the man page
> >doesn't say -- although obviously there's not much you can do until you 
> >have
> >a display pointer.
> 
> Thanks, Maurice, for your response. I mentioned XOpenDisplay because that
> was in the call stack of Andrew's example, but the problem there must lie
> elsewhere because I tried a simple test routine with XOpenDisplay (see
> below), and it generates no memory management errors (except for some
> unfreed memory).

Hi Alan,

In both the errors I found the uninitialised memory block was allocated
in XOpenDisplay, but the error actually occured in subsequent calls to X
functions like XAllocColor. Like you I have tried a simple example, but
this does not generate any errors. I will continue experimenting.

Andrew