On Thu, 12 Feb 2009, [email protected] wrote:
> On Thu, 12 Feb 2009, [email protected] wrote:
>
> >
> > > So, if SocketReceive returned an uninitialised value then it can cause
> > > this? So that tells me that I should review SockReceive in more detail to
> > > try and determine how that could happen.
> >
> > Do you have the source code of SockReceive and the functions it calls? Can
> > you
> > show it?
> >
> In the case that is reporting the error it is just a wrapper around
> SSL_Read().
> I am going to try a few things first. If I don't figure anything out soon
> I'll
> send more info.
>
Ok, I rebuilt OpenSSL with the -DPURIFY and I was able to get a more useful
warning reported by valgrind. It is now warning me about SocketSSLReceive()
which was called SocketReceive() from the previous warning.
int bytes = SSL_read( socket->ssl.conn, (void *)buffer, length);
if ( bytes > 0 ) {
...
It warns about the if line above. After googling around a bit I've found people
claiming that SSL should run clean. So, now I have to wonder if it is our SSL
BIO.... Guess I've got more code to look through.
Micah
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
