Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Beginner
18 Views

PDB files for IPP DLLs

Hi I would like to know if any one knows where one could fine symbol files for the DLLS provided with IPP.

The situation is that (because of some bug) my code would crash inside some IPP function. Without the symbol file the call stack doesn't work and I cannot debug the function which called the IPP function and solve the problem.

Has any one have an idea how to handle this issue ?

0 Kudos
4 Replies
Highlighted
18 Views

Hello,
we do not provide debug information for IPP DLLs, so in case of run time issue you may submit bug report with description of what IPP function cause crash and which parameters you use at that function call.
Regards,
Vladimir

0 Kudos
Highlighted
Beginner
18 Views

Hello,
we do not provide debug information for IPP DLLs, so in case of run time issue you may submit bug report with description of what IPP function cause crash and which parameters you use at that function call.
Regards,
Vladimir


This isn't the problem we are facing. Usually, it isn't a crashed caused by Intel IPP. The problem is that a bug in the software developed by the user, provides invalid parameters to the IPP function (for example, providing an out of rangeregion to an image processing function which causes a general protection error).

When running the system it then crashes somewhere inside the IPP Dll. Because we have no PDB file (no need for source code, only PDB file is sufficient) we cannot use the callstack to trace back to the root of the problem and debug it. Usually when this happens, you have no clue which function called it and what were the parameters. You don't even know in which IPP function you are currently located.

The debugging process becomes even more difficult when we are dealing with post-mortem debugging. That is, debugging using a MINI-DUMP file. In this case, you can't "re-run" the system and hope to catch the bug. You want to use the dump file containing the stack and context using the VS debugger and attempt to find the bug.

Microsoft for example, provide a PDB file for each DLL in the system using public symbol servers, so if we crash someone inside microsoft API, there is no problem to stack track back to the source.

It would be good if Intel could provide the same functionality.


Oded
0 Kudos
Highlighted
18 Views

Hello,

then I would recommend you to submit this as a feature request to Intel Premier Support, so it will be reconsidered at the next IPP version planning stage

Regards,
Vladimir
0 Kudos
Highlighted
Beginner
18 Views

Quoting - ohanson

This isn't the problem we are facing. Usually, it isn't a crashed caused by Intel IPP. The problem is that a bug in the software developed by the user, provides invalid parameters to the IPP function (for example, providing an out of rangeregion to an image processing function which causes a general protection error).

When running the system it then crashes somewhere inside the IPP Dll. Because we have no PDB file (no need for source code, only PDB file is sufficient) we cannot use the callstack to trace back to the root of the problem and debug it. Usually when this happens, you have no clue which function called it and what were the parameters. You don't even know in which IPP function you are currently located.

The debugging process becomes even more difficult when we are dealing with post-mortem debugging. That is, debugging using a MINI-DUMP file. In this case, you can't "re-run" the system and hope to catch the bug. You want to use the dump file containing the stack and context using the VS debugger and attempt to find the bug.

Microsoft for example, provide a PDB file for each DLL in the system using public symbol servers, so if we crash someone inside microsoft API, there is no problem to stack track back to the source.

It would be good if Intel could provide the same functionality.

Wondering for my own case, can you get the callstack if you use static linking of IPP functions inside your program/dll ?

regards
0 Kudos