Analyzers
Talk to fellow users of Intel Analyzer tools (Intel VTune™ Profiler, Intel Advisor)
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.

Intel inspector

Purnachandra
Beginner
2,327 Views

Hi,
Need support to run the intel -inspector tool to get the memory leak status for Intel- FlexRAN code(21.03) for l1app & testmac.
PS:- We are planning to validate memory leak in FlexRAN code for all channel wise unit testing.

0 Kudos
6 Replies
JananiC_Intel
Moderator
2,286 Views

Hi,


Thanks for posting in Intel forums.


We are working on this. We will get back to you.


Regards,

Janani Chandran


0 Kudos
Purnachandra
Beginner
2,279 Views

Thanks, Janani.

Please check and provide the steps to get the memory leak for flexran code for the Linux environment. 

0 Kudos
Purnachandra
Beginner
2,264 Views

hi ,
Response awaited. need to know the steps to run the inspector tool with FlexRAN(intel-L1 code).

Thanks

0 Kudos
JananiC_Intel
Moderator
2,264 Views

Hi,



Sorry for the delay. You can follow the below link to enable Inspector to detect custom memory allocations.


https://www.intel.com/content/www/us/en/develop/documentation/inspector-user-guide-windows/top/api-support/apis-for-custom-memory-allocation.html


Regards,

Janani Chandran


0 Kudos
Purnachandra
Beginner
2,259 Views

Hi,
I have tried this on a Linux environment setup but could get an app-based memory leak. If you can extend support and get the steps to run the inspector procedures for intel FlexRAN code(21.03) would be helpful.

Refereed link:- 
https://www.intel.com/content/www/us/en/develop/documentation/inspector-user-guide-linux/top/api-support/apis-for-custom-memory-allocation.html


Thanks

0 Kudos
JananiC_Intel
Moderator
2,227 Views

Hi,


We are providing you support via our priority channel and your issue will be addressed there so we are closing this thread.


Regards,

Janani Chandran


0 Kudos
Reply