[openssl-dev] [openssl.org #3623] faulting module ssleay32.dll, version 0.0.0.0, fault address 0x00010c8b.

[Matt Caswell via RT]

Hi Vijendra

There is insufficient information from your description to determine whether
this is a fault with OpenSSL or with your application. If this is still an
issue for you, please raise it on the openssl-users email list.

Since it cannot be determined that there is a problem OpenSSL itself I am
closing this ticket for now.

Regards

Matt

___
openssl-dev mailing list
openssl-dev@openssl.org
https://mta.opensslfoundation.net/mailman/listinfo/openssl-dev

Re: [openssl-dev] [openssl.org #3623] faulting module ssleay32.dll, version 0.0.0.0, fault address 0x00010c8b.

[Vijendra Boopathy via RT]

Hi,

The exact error which i faced in Event log are given below.

Faulting application name: aeagent.exe, version:0.0.0.0, time
stamp:0x53e1f20f
Faulting module name: SSLEAY32.dll, version:0.0.0.0, time stamp: 0x405a2628
Exception code: 0xc005
Fault offset: 0x00010c8b
Faulting process id : 0x1bc0

What is that mean??
I googled with this error,
firefox faced the same error and they gave workaround was replace the
latest version of dll.
I did the same but no use..

Please tell what i want to do??


On 5 December 2014 at 22:01, Andy Polyakov via RT  wrote:

> > Am using openssl for my monitoring tools and i have facing *faulting
> module
> > ssleay32.dll, version 0.0.0.0, fault address 0x00010c8b *in  application
> > log and its all type of windows OS
> > May i know that it is known issue or new issue,if it is known issue
> please
> > provide issue id.
> >
> > Kindly help ASP...
> >
> > Note : am using latest openssl (openssl-1.0.1j.tar.gz
> > )
>
> Specific fault address does not provide sufficient information by itself
> and it's impossible to tell anything from it. You refer to source code,
> and if you compile it yourself, you'll have symbol information as .pdb
> files that you can use to identify failing function. You should be able
> to use it together with crash dump information in debugger to identify
> failing function and collect so called stack back-trace. Only then it
> would be possible to make some assessment about nature of the problem.
> [As for "crash dump", I don't think meaningful crash dump generation is
> enabled by default nowadays, i.e. you would have to configure it, google
> should be your friend].
>
>
>
>


-- 
Thanks & Regards
vijendra boopathy.k

___
openssl-dev mailing list
openssl-dev@openssl.org
https://mta.opensslfoundation.net/mailman/listinfo/openssl-dev