Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
29281 Discussions

How can I debug CXML?

sangsul
Beginner
‎08-28-2002 04:02 PM
852 Views
Dear CXML team,

When runnning my code using CXML direct sparse matrix solver, an error detected during run. it seems to be from changing nonsymetric matrix to symmetricstructured matrix. but I can't understand what's wrong. How can it be debugged? Can CXML give me some text error messages not access violation? Error message says:


Initializing the solver.
Defining structure.
forrtl: severe (157): Program Exception - access violation
Image PC Routine Line Source
flame.exe 00493033 Unknown Unknown Unknown
Unknown CDCDCDCD Unknown Unknown Unknown
Press any key to continue

Sangsu Lee
0 Kudos

Link Copied

1 Reply
Steven_L_Intel1
Employee
‎08-28-2002 05:04 PM
852 Views
Just a comment - this is not the place to ask questions of the "CXML team". If you would like to submit a support request, see http://www.compaq.com/fortran/support/visual.html Be sure to supply a complete example that reproduces the problem.

If you run the program in the debugger, it should stop at the point of the error. You may need to change the context view to show the caller, if the access violation is occurring inside CXML. Then you should check your arguments to be sure they are correct.

Steve
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.