- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I spent today tracking down an bug in my code. I used libgmalloc (via setenv DYLD_INSERT_LIBRARIES /usr/lib/libgmalloc.dylib), which turned the bug into a crash (this is the correct behavior). I eventually figured out that the OpenCV library was crashing on load. From there, I built a debug version of OpenCV and narrowed the problem down to cxswitcher.cpp. In there, I discovered that the crash occurred when the IPP library was being loaded.
A simpler test case, which doesn't require OpenCV is:
cat > ipp_crash.cpp
int main (int argc, char * argv[]) { return 0; }
^D
g++ -o ipp_crash -lippcore -lippcv -lguide -L/Library/Frameworks/Intel_IPP.framework/Libraries ipp_crash.cpp
setenv DYLD_INSERT_LIBRARIES /usr/lib/libgmalloc.dylib
./ipp_crash
You will get a segmentation fault and a core if you have them turned on. I can't go debug any farther because I don't have source for libippcv.
-- Sal
smile.
A simpler test case, which doesn't require OpenCV is:
cat > ipp_crash.cpp
int main (int argc, char * argv[]) { return 0; }
^D
g++ -o ipp_crash -lippcore -lippcv -lguide -L/Library/Frameworks/Intel_IPP.framework/Libraries ipp_crash.cpp
setenv DYLD_INSERT_LIBRARIES /usr/lib/libgmalloc.dylib
./ipp_crash
You will get a segmentation fault and a core if you have them turned on. I can't go debug any farther because I don't have source for libippcv.
-- Sal
smile.
Link Copied
3 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Sorry, I cannot reproduce a crash. I followed your instructions exactly and recevied the following warning:
$ ./ipp_crash
Allocations will be placed on word (4 byte) boundaries.
- Small buffer overruns may not be noticed.
- Applications using AltiVec instructions may fail.
GuardMalloc-11
The system I tested on is:
- Mac OS X 10.4.8
- Darwin 8.8.1
- Intel Core2 Duo
For the fastest response, please submit problem reports (including test cases) to Intel Premier Support at https://premier.intel.com.
Regards,
--Amanda S.
Intel Corp.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I reproduced the crash here. It says:
$ ./ipp_crash
Allocations will be placed on word (4 byte) boundaries.
- Small buffer overruns may not be noticed.
- Applications using AltiVec instructions may fail.
GuardMalloc-11
Segmentation fault
Tested on Mac OS X 10.4.9, build 8P2137 (Darwin 8.9.1) running on Intel Core 2 Duo.
$ ./ipp_crash
Allocations will be placed on word (4 byte) boundaries.
- Small buffer overruns may not be noticed.
- Applications using AltiVec instructions may fail.
GuardMalloc-11
Segmentation fault
Tested on Mac OS X 10.4.9, build 8P2137 (Darwin 8.9.1) running on Intel Core 2 Duo.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I've submitted the report through the bug tracking system, though I don't have any more information. I have, however, reproduced it on several systems running the same OS.
Thank you for getting back to me!
-- Sal
smile.
![](/skins/images/7FC17B7B85029576C25F1E43CE255B51/responsive_peak/images/icon_anonymous_message.png)
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