Hello,

o Tom van der Geer [06/02/09 12:30]:
Stefan Sayer writes:


For some reason it evaluates (_ssl_ssl != (SSL *) NULL) as true in XmlRpcSource.cpp:34 to be able to reach line the SSL_shutdown at line 35. In the constructor of XmlRpcSource the _ssl_ssl parameter is set to NULL (see revision r1249) and I can't find any other place where _ssl_ssl is changed to another value.

does this really happen with r1269 applied? Are you using SSL at all? Seems to me like you need to rebuild (maybe make clean did not clean your xmlrpc++).

Stefan
Yes, it happened with r1296 applied and "make clean" cleans the xmlrpc++ dirs fine.

I'm now focussing on the XmlRpcServer in stead of the XmlRpcClient part, because I'm not sure it has anything to do with XmlRpcClient. I noticed that XmlRpcServer extends XmlRpcSource, but in it's constructor it's not setting some member variables of XmlRpcSource (like _ssl_ssl) so they could be initialized with an incorrect value. I[ve now changed the implementation of the XmlRpcServer constructor to:

XmlRpcServer::XmlRpcServer() : XmlRpcSource()
the base constructor is called automatically - with default arguments, too.

{
(...)
}

And started another batch of test calls.
instead of waiting for some uninitialized memory to happen to contain faulty values, you can get that simpler by running sems in valgrind and checking for 'uninitialized bytes used' type of warnings.

Stefan

Regards,

Tom

--
Stefan Sayer
VoIP Services

[email protected]
www.iptego.com

IPTEGO GmbH
Wittenbergplatz 1
10789 Berlin
Germany

Amtsgericht Charlottenburg, HRB 101010
Geschaeftsfuehrer: Alexander Hoffmann
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems

Reply via email to