Intel® Integrated Performance Primitives
Deliberate problems developing high-performance vision, signal, security, and storage applications.
6716 Discussions

Access violation calling ippsExp_64fc_A53 in IPP 2018.0.124

Keith_W_
Beginner
494 Views

I am getting an access violation when calling ippsExp_64fc_A53 in IPP 2018.0.124

Code to reproduce:

Ipp64fc* b1{ ippsMalloc_64fc(1025) };
Ipp64fc* b2{ ippsMalloc_64fc(1025) };

for (int i = 0; i < 1025; i++)
{
	b1.re = 1;
	b1.im = 0;
}

ippsExp_64fc_A53(b1, b2, 1025);

ippsFree(b1);
ippsFree(b2);

My machine specs:

OS: Windows 10 Professional
IPP version: 2018.0.124
Processor: Intel Core i7-4790
Memory: 32 GB RAM
IDE: Visual Studio 2017 (debug build 64-bits)

The fix is to use ippsExp_64fc_A50 which works.

0 Kudos
4 Replies
Keith_W_
Beginner
494 Views

I should add that this only occurs when I enable gflags to catch memory issues:

gflags /p /enable app.exe /full

 

0 Kudos
Jonghak_K_Intel
Employee
494 Views

Hi Keith,

 

 Can you provide a screenshot of the access violation message and some information about how gflags detects the memory issues and how it affects the working process?

 

thank you

0 Kudos
Keith_W_
Beginner
494 Views

You can learn more about gflags here (it is part of the Microsoft Windows SDK for detecting memory leaks and buffer overruns):

https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/gflags

Screen shot of the error:

https://imgur.com/a/yKTNB

Replacing ippsExp_64fc_A53 with ippsExp_64fc_A50 resolves the problem.

0 Kudos
Jonghak_K_Intel
Employee
494 Views

Thanks for the information.

 

The issue has been escalated to the engineering to root cause.

We need some time to see what actually happens when gflags gets enabled.

Will get back to you as soon as possible.

 

Thank you.

0 Kudos
Reply