Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.misc -> Re: Purify(Windows NT) is reporting FIM(Free Invalid Memory) in OCIServerAttach()
Abhisek wrote:
> Hi,
>
> I am using OCI in my application for about an year.Recently I found
> some crahes in my OCI wrapper.To figure out I ran my application
under
> purify and figured out that it is reporting Free Invalid Memory (FIM)
> in OCIServerAttach().The stack is given below:
>
> [E] FIM: Freeing invalid memory in LocalFree {1 occurrence}
> Address 0x00152e80 points into a HeapAlloc'd block in unallocated
> region of the default heap
> Location of free attempt
> LocalFree+0xc [KERNEL32.dll ip=0x67f01dab]
> ??? [security.dll ip=0x76e71a88]
> AcquireCredentialsHandleA+0x54 [security.dll ip=0x76e73ee9]
> naunts5+0xf98 [orannts8.dll ip=0x64501f98]
> naunts+0xf10 [orannts8.dll ip=0x64505030]
> sntseltst+0x269a [oran8.dll ip=0x60b6484a]
> naconnect+0x13a4 [oran8.dll ip=0x60b02a54]
> naconnect+0x964 [oran8.dll ip=0x60b02014]
> naconnect+0x123 [oran8.dll ip=0x60b017d3]
> nsmore2recv+0xc93 [oran8.dll ip=0x60b53bb3]
> nsmore2recv+0x6ba [oran8.dll ip=0x60b535da]
> nscall+0x6f3 [oran8.dll ip=0x60b3f2d3]
> niotns+0x6c7 [oran8.dll ip=0x60b155e7]
> osncon+0x44c [oran8.dll ip=0x60b610cc]
> xaolog+0x1f533 [OraClient8.Dll ip=0x604b0c93]
> xaolog+0x26d3e [OraClient8.Dll ip=0x604b849e]
> upiah0+0x63 [OraClient8.Dll ip=0x6047f933]
> kpuatch+0x30a [OraClient8.Dll ip=0x604246da]
> OCIServerAttach+0x20 [OraClient8.Dll ip=0x60401340]
> OCIServerAttach+0x2b [OCI.dll ip=0x1000596b]
>
> I am calling OCIServerAttach() in a following way:
> OCIServerAttach(srvhp, errhp,(text *)dbName, strlen(dbName),0);
> where dbName is a member variable of my class.Its a character array
> that I have allocated on heap and its size is 256 bytes.
>
> My application is a multitier application running on Windows NT.
>
> Please help me out.Is any thing wrong in the usage?
>
> Regards
> Abhishek
Hello Abhisek,
I am getting the similar error from purify for OCIServerAttach()
function call.
Did you manage to identify the problem?
Kindly advice me how to overcome this issue.
Regards,
Sreedharan
Received on Mon Dec 13 2004 - 00:15:43 CST