- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When I build my project in debug mode, with O1 or O2, a fortcom.exe is choking on one of my files; it keeps using very little CPU time, and yet picks up 600MB of virtual memory.
When I'm done with building the project, I get
Error 529 error PRJ0019: A tool returned an error code
And I get no additional details...
If I run the debug mode with no-opt, all is well except the code takes way too long to execute.
Building it in release mode, I get no problems.
I've noticed a great way to reproduce this bug is to rename my output file, and build the code again.
To make this all more fun, the debug version of the code gives me different numerical answers versus the release version.
Debug flags:
/nologo /Zi /QxN /Qzero /fpe:0 /module:"$(INTDIR)/" /object:"$(INTDIR)/" /traceback /check:bounds /libs:static /threads /dbglibs /c
Additional Options:
/fp:precise
Linker:
/OUT:"Debug/App.exe" /INCREMENTAL /NOLOGO /MANIFEST /MANIFESTFILE:"C:MyPathdebugApp.exe.intermediate.manifest" /DEBUG /PDB:"Debug/App.pdb" /SUBSYSTEM:CONSOLE
Release Flags:
/nologo /QxN /Qzero /fpe:0 /module:"$(INTDIR)/" /object:"$(INTDIR)/" /libs:static /threads /c
Additional Options:
/fp:precise
Linker:
/OUT:"Release/App.exe" /INCREMENTAL:NO /NOLOGO /MANIFEST /MANIFESTFILE:"C:MyPath eleaseApp.exe.intermediate.manifest" /SUBSYSTEM:CONSOLE
When I'm done with building the project, I get
Error 529 error PRJ0019: A tool returned an error code
And I get no additional details...
If I run the debug mode with no-opt, all is well except the code takes way too long to execute.
Building it in release mode, I get no problems.
I've noticed a great way to reproduce this bug is to rename my output file, and build the code again.
To make this all more fun, the debug version of the code gives me different numerical answers versus the release version.
Debug flags:
/nologo /Zi /QxN /Qzero /fpe:0 /module:"$(INTDIR)/" /object:"$(INTDIR)/" /traceback /check:bounds /libs:static /threads /dbglibs /c
Additional Options:
/fp:precise
Linker:
/OUT:"Debug/App.exe" /INCREMENTAL /NOLOGO /MANIFEST /MANIFESTFILE:"C:MyPathdebugApp.exe.intermediate.manifest" /DEBUG /PDB:"Debug/App.pdb" /SUBSYSTEM:CONSOLE
Release Flags:
/nologo /QxN /Qzero /fpe:0 /module:"$(INTDIR)/" /object:"$(INTDIR)/" /libs:static /threads /c
Additional Options:
/fp:precise
Linker:
/OUT:"Release/App.exe" /INCREMENTAL:NO /NOLOGO /MANIFEST /MANIFESTFILE:"C:MyPath eleaseApp.exe.intermediate.manifest" /SUBSYSTEM:CONSOLE
Link Copied
3 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Please report this to Intel Premier Support and include everything needed to reproduce the problem. You should also look at the buildlog.htm or .txt output in the Debug subfolder to see if there's additional information there.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm having issues with the support link as we duscussed on another thread. Does emailing developer-dot-support-at-intel-dot-com work just as well? I have not received an acknowledgement from them.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
No - that email address has been discontinued. or at best gets sent to some generic group that may take some time to forward the request. If you are having difficulty using the Premier Support web site, there is a link to a support page on the login screen or you can write to quad.support at intel.com and ask for help using Premier Support. Do NOT send your compiler support request to that address.

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