- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi all,
I am a recent user of fortran on mac and keep getting this error when I execute my code:
error for object 0x100201c78: incorrect checksum for freed object - object was probably modified after being freed.
*** set a breakpoint in malloc_error_break to debug
error for object 0x100201c78: incorrect checksum for freed object - object was probably modified after being freed.*** set a breakpoint in malloc_error_break to debugAny idea on what the problem is?
It seems related to memory allocation....
Thanks!
Marco
Link Copied
3 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Your program is writing outside allocated memory, or are using a pointer after freeing it. This can be very difficult to diagnose, unfortunately.
What I usually do when confronted with such a problem, and where I can't use Intel Inspector XE (which doesn't support Mac, unfortunately for you), is backing up from the point of the error and seeing which code I can selectively remove and still have the error occur. This can help you locate the error source. You may also want to turn on all run-time checking (-C) and also build with -warn interface.
What I usually do when confronted with such a problem, and where I can't use Intel Inspector XE (which doesn't support Mac, unfortunately for you), is backing up from the point of the error and seeing which code I can selectively remove and still have the error occur. This can help you locate the error source. You may also want to turn on all run-time checking (-C) and also build with -warn interface.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dear Steve,
unofrtunately I keep getting this problem. In particular when i simply try to print something out of my code. No matter what is (even a simple "hello") I still get the same error.
Any idea??
Thanks
-marco
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Same answer, really - something is corrupting memory. The PRINT just happens to be the place it gets reported. Same advice as I gave earlier.

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