Finding Run-time Error

Finding Run-time Error

Hello all,

I have an app that compiles & runs fine using CVF, and I am trying to compile & run it w/ IFC on RH8.

It throws up an *Address Error* that I am having trouble fixing. I have recompiled with -C but I can't figure out how to get the debugger to stop _at the error_ in the code. I'm using DDD to debug using the command
ddd -ladebug -debugger idb a.out
as suggested elsewhere in this thread. The app runs, but dies with a run-time error. However, DDD doesn't show me or stop where the error occurs.

Any thoughts?


3 posts / 0 nouveau(x)
Dernière contribution
Reportez-vous à notre Notice d'optimisation pour plus d'informations sur les choix et l'optimisation des performances dans les produits logiciels Intel.

I've dealt with "*Address Errors*" more than a few times in the past, and every one behaves the same in the debugger:

*Address Error*

Is the problem that the process doesn't seem to stop in idb, so that you can't ask for a stack trace? Or are you able to get a stack trace, but you think it's past the point where the error occurred?

Intel Developer Support

For on-line assistance:
For product support information:
* Intel and Pentium are registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries
* Other names and brands may be claimed as the property of others

Brandon Hewitt
Technical Consulting Engineer

For 1:1 technical support:

Software Product Support info:

Might you try increasing the diagnostic level
with the '-dN' option, e.g. -d2?

Then maybe the runtime error message, absent any debugger, willl still give you the actual line number.

On the other hand I've generally found that when I have a nasty run-time bug I switch back to my NAG compiler, which is very reliable with excellent diagnostics. Its code generaiton is not as good as Intel's though.

Laisser un commentaire

Veuillez ouvrir une session pour ajouter un commentaire. Pas encore membre ? Rejoignez-nous dès aujourd’hui