- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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?
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?
Link Copied
1 Reply
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
![](/skins/images/D2683F18326913BBA0436CB7114DD569/responsive_peak/images/icon_anonymous_message.png)
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