- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, all
I'm using intel IPP V4.1, and also set "Process OpenMP Directive" to QOpenMP touse openmp to do multi-threading in the same dll in my system. Passed building and linking. (My compiler is VS 2002 + intel compiler 9.0, runningin windows xp system, platform: intel Core2 DUO).
System hangs up every time in runtime, the call stack from VS2002 is :
ntdll.dll!_KiFastSystemCallRet@0()
ntdll.dll!_ZwWaitForSingleObject@12() + 0xc
kernel32.dll!_WaitForSingleObjectEx@12() + 0x8b
kernel32.dll!_WaitForSingleObject@8() + 0x12
libguide40.dll!02013869()
libguide40.dll!0201485c()
libguide40.dll!0200440a()
libguide40.dll!02004e57()
libguide40.dll!02008fd9()
libguide40.dll!02009adc()
libguide40.dll!0200582d()
libguide40.dll!0200b4b6()
> 3DCored.dll!bMakeImage(const VolumeQuad *
the call stack from windbg is:ntdll!KiFastSystemCallRet
ntdll!ZwWaitForSingleObject+0xc
kernel32!WaitForSingleObjectEx+0xa8
kernel32!WaitForSingleObject+0x12
WARNING: Stack unwind information not available. Following frames may be wrong.
libguide40!_kmpc_ssp_set_max_threads+0x179
libguide40!_kmp_reap_worker+0x4ec
libguide40!_kmp_wait_sleep+0x13e
libguide40!_kmp_release+0xa27
libguide40!_kmp_fork_call+0x39a1
libguide40!_kmpc_invoke_task_func+0x194
libguide40!_kmp_fork_call+0x1f5
libguide40!_kmpc_fork_call+0x26
3DCored!bMakeImage+0x1300
Is anyboby can tell me the root cause? if this is related to my intel compiler openmp version and IPP Version? and if any requirement to using openmp in intel compilerwith iPP library V4.1?
Thanks.
I'm using intel IPP V4.1, and also set "Process OpenMP Directive" to QOpenMP touse openmp to do multi-threading in the same dll in my system. Passed building and linking. (My compiler is VS 2002 + intel compiler 9.0, runningin windows xp system, platform: intel Core2 DUO).
System hangs up every time in runtime, the call stack from VS2002 is :
ntdll.dll!_KiFastSystemCallRet@0()
ntdll.dll!_ZwWaitForSingleObject@12() + 0xc
kernel32.dll!_WaitForSingleObjectEx@12() + 0x8b
kernel32.dll!_WaitForSingleObject@8() + 0x12
libguide40.dll!02013869()
libguide40.dll!0201485c()
libguide40.dll!0200440a()
libguide40.dll!02004e57()
libguide40.dll!02008fd9()
libguide40.dll!02009adc()
libguide40.dll!0200582d()
libguide40.dll!0200b4b6()
> 3DCored.dll!bMakeImage(const VolumeQuad *
the call stack from windbg is:ntdll!KiFastSystemCallRet
ntdll!ZwWaitForSingleObject+0xc
kernel32!WaitForSingleObjectEx+0xa8
kernel32!WaitForSingleObject+0x12
WARNING: Stack unwind information not available. Following frames may be wrong.
libguide40!_kmpc_ssp_set_max_threads+0x179
libguide40!_kmp_reap_worker+0x4ec
libguide40!_kmp_wait_sleep+0x13e
libguide40!_kmp_release+0xa27
libguide40!_kmp_fork_call+0x39a1
libguide40!_kmpc_invoke_task_func+0x194
libguide40!_kmp_fork_call+0x1f5
libguide40!_kmpc_fork_call+0x26
3DCored!bMakeImage+0x1300
Is anyboby can tell me the root cause? if this is related to my intel compiler openmp version and IPP Version? and if any requirement to using openmp in intel compilerwith iPP library V4.1?
Thanks.
Link Copied
1 Reply
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
any specific reason you still use several year old IPP product? I would recommedn you to try the latest version which is IPP 6.1 update 2
Regards,
Vladimir

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