- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
this is a trivial question, and I am only posting since I simply couldn't find the (perhaps obvious) answer even after browsing several manuals. Any solution, however obvious, is greatly appreciated.
When a compiled binary of mine segfaults, it would be really nice to simply get the source file and line number where this occurred. All that I can see indicates that ifort should be able to do this, but even with -O0, -g, idb, and the source directory specified on the idb command line, I simply get:
Image PC Routine Line Source
localorb.101006.m 0854E55C Unknown Unknown Unknown
localorb.101006.m 0854CCF5 Unknown Unknown Unknown
localorb.101006.m 08522EA6 Unknown Unknown Unknown
localorb.101006.m 084FDC44 Unknown Unknown Unknown
localorb.101006.m 081C7CDC Unknown Unknown Unknown
localorb.101006.m 0804CD30 Unknown Unknown Unknown
localorb.101006.m 0804A8BE Unknown Unknown Unknown
libc.so.6 403B4500 Unknown Unknown Unknown
localorb.101006.m 0804A7E1 Unknown Unknown Unknown
in conjunction with the segfault. I have tried various other combinations of flags, but have never been able to get line numbers out of ifort-compiled code, or even a hint as to what the problem may be.
With all other compilers that I typically try (g95, xlf, decfortran) this works out of the box, and the ifort manuals imply at places that it should work out of the box here, also.
Thanks for any hints!
this is a trivial question, and I am only posting since I simply couldn't find the (perhaps obvious) answer even after browsing several manuals. Any solution, however obvious, is greatly appreciated.
When a compiled binary of mine segfaults, it would be really nice to simply get the source file and line number where this occurred. All that I can see indicates that ifort should be able to do this, but even with -O0, -g, idb, and the source directory specified on the idb command line, I simply get:
Image PC Routine Line Source
localorb.101006.m 0854E55C Unknown Unknown Unknown
localorb.101006.m 0854CCF5 Unknown Unknown Unknown
localorb.101006.m 08522EA6 Unknown Unknown Unknown
localorb.101006.m 084FDC44 Unknown Unknown Unknown
localorb.101006.m 081C7CDC Unknown Unknown Unknown
localorb.101006.m 0804CD30 Unknown Unknown Unknown
localorb.101006.m 0804A8BE Unknown Unknown Unknown
libc.so.6 403B4500 Unknown Unknown Unknown
localorb.101006.m 0804A7E1 Unknown Unknown Unknown
in conjunction with the segfault. I have tried various other combinations of flags, but have never been able to get line numbers out of ifort-compiled code, or even a hint as to what the problem may be.
With all other compilers that I typically try (g95, xlf, decfortran) this works out of the box, and the ifort manuals imply at places that it should work out of the box here, also.
Thanks for any hints!
Link Copied
1 Reply
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Try adding -traceback. This is not related to debugging.

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