- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am in the process of porting some Fortran PowerStation code to IVF 8.1 / VS.NET 2003. The code is for DLLs consisting of several F77 libs wrapped by a thin layer of C++ functions, which constitutes the DLLs interface.
I am unable to get proper traceback information for "severe" runtime errors. The callstack in the runtime error window lists "unknown" for file and line number for all entries in my DLL. When breaking execution to check in the VS.NET debugger, the call stack there is sometimes spot on, and sometimes totally wrong and very truncated.
Traceback and full debug is set for all the IVF lib projects in the DLL.
Doing the "iterative binary search using breakpoints" thing to locate out of bounds errors feels a bit wrong, when the runtime is presumably perfectly capable of identifying the source of the problem...
Regards,
Einar Rune Haugnes
I am unable to get proper traceback information for "severe" runtime errors. The callstack in the runtime error window lists "unknown" for file and line number for all entries in my DLL. When breaking execution to check in the VS.NET debugger, the call stack there is sometimes spot on, and sometimes totally wrong and very truncated.
Traceback and full debug is set for all the IVF lib projects in the DLL.
Doing the "iterative binary search using breakpoints" thing to locate out of bounds errors feels a bit wrong, when the runtime is presumably perfectly capable of identifying the source of the problem...
Regards,
Einar Rune Haugnes
Link Copied
1 Reply
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Please submit an example of this to Intel Premier Support so that we can look at it.

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