- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I use IPP statically linked to my application.
While building my project I encountered that VC linker is not able to create my binary with debug information because ippcore_t.lib has corrupted debug information.
I got linker error:
ippcore_t.lib(pscpudefas.obj) : fatal error LNK1103: debugging information corrupt; recompile module
Because of this I can not debug my code :(
Is there any solution/workaround of this issue?
Is ippcore_t.lib linkable in debug mode available?
While building my project I encountered that VC linker is not able to create my binary with debug information because ippcore_t.lib has corrupted debug information.
I got linker error:
ippcore_t.lib(pscpudefas.obj) : fatal error LNK1103: debugging information corrupt; recompile module
Because of this I can not debug my code :(
Is there any solution/workaround of this issue?
Is ippcore_t.lib linkable in debug mode available?
1 Solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You can easily mix debug and non-debug object code during linking, so ippcore_t.lib can be used in debug project configuration. Regarding fatal error, there was a forum topic about this issue 2-3 forum pages ago (http://software.intel.com/en-us/forums/showthread.php?t=102963&o=a&s=lr). Check if it could help.
Regards,
Sergey
Sergey
Link Copied
2 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You can easily mix debug and non-debug object code during linking, so ippcore_t.lib can be used in debug project configuration. Regarding fatal error, there was a forum topic about this issue 2-3 forum pages ago (http://software.intel.com/en-us/forums/showthread.php?t=102963&o=a&s=lr). Check if it could help.
Regards,
Sergey
Sergey
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you.
Microsoft HotFix KB949009 did help.
However I would prefer more explicit reply like:
- - - - - - - - - - - - - - - - - -- - - - - - - - -- - - - - - - - -
It is known issue of MS linker.
Check if you installed VS2005 HotFix KB949009
https://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=18623
For reference, similar issues reported are:
Link to message 1
Link to message 2
...
- - - - - - - - - - - - - - - - - -- - - - - - - - -- - - - - - - - -
( Think, it is advice )
Thank you anyway.
Following chain of links helped me to solve my task.
Microsoft HotFix KB949009 did help.
However I would prefer more explicit reply like:
- - - - - - - - - - - - - - - - - -- - - - - - - - -- - - - - - - - -
It is known issue of MS linker.
Check if you installed VS2005 HotFix KB949009
https://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=18623
For reference, similar issues reported are:
Link to message 1
Link to message 2
...
- - - - - - - - - - - - - - - - - -- - - - - - - - -- - - - - - - - -
( Think, it is advice )
Thank you anyway.
Following chain of links helped me to solve my task.
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page