Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
28632 Discussions

Cannot get useful traceback in idb for a SIGSEGV

luang-prabang
Beginner
‎09-10-2010 09:18 AM
303 Views
Greetings:

I am trying to track down a seg fault in a fortran program and idb is not helping.

It tells me this:

000000000048bdea in allocCstr () in /blah/blah/program
0x0000000000542ae4 at /blah/blah/program section .text offset 0x0000000000142ae4

I have no problem getting proper line numbers if I set breakpoints and stop at them, but I cannot figure out how to get it to tell me the call stack that leads to allocCstr.

Also, I tried 'export f77_dump_flag=TRUE', to no avail.

Suggestions?
0 Kudos

Link Copied

1 Reply
Martyn_C_Intel
Employee
‎09-10-2010 02:51 PM
303 Views

You might trymy suggestions at
http://software.intel.com/en-us/articles/tips-for-debugging-run-time-failures-in-intel-fortran-applications/

If the call stack is getting corrupted, you need to catch the error at an earlier point.

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.