- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Dear all,
I have a problem with my code that I would you like you help me to understand.
It compiles well, but when I execute it, if the size of the coputation is "large" it gives me the following answer:
forrtl: severe (174): SIGSEGV, segmentation fault occurred
This is not really surprising. What I find ununderstandable for me is that if I compile with the -traceback options, the compiler tells me that the error happens on a line that opens a file for writing:
open(10,file='../Output_5/R_hr',form='binary',status='unknown')
If I comment this and its related lines, everything works fine. At the beginning I thought it could be a problem of the size or the memory or of the stack but now I do not know.
I tried also to better investigate by means of idb, and the message I receive at the beginning, before of running, is
[1] stopped at [ function main(...) 0x08049483]
I do not know if the two errors are related. Is there anybody who can help me?
Thanks in advance,
Giuseppe
I have a problem with my code that I would you like you help me to understand.
It compiles well, but when I execute it, if the size of the coputation is "large" it gives me the following answer:
forrtl: severe (174): SIGSEGV, segmentation fault occurred
This is not really surprising. What I find ununderstandable for me is that if I compile with the -traceback options, the compiler tells me that the error happens on a line that opens a file for writing:
open(10,file='../Output_5/R_hr',form='binary',status='unknown')
If I comment this and its related lines, everything works fine. At the beginning I thought it could be a problem of the size or the memory or of the stack but now I do not know.
I tried also to better investigate by means of idb, and the message I receive at the beginning, before of running, is
[1] stopped at [
I do not know if the two errors are related. Is there anybody who can help me?
Thanks in advance,
Giuseppe
Link Copied
1 Reply
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Couldn't you verify whether it is a stack problem by increasing your limit?
Are you asking for suggestions about how to investigate details, how your application might run out of space when allocating buffers for a newly opened file? You aren't at all clear about your question, and you leave us guessing about your software versions.
Are you asking for suggestions about how to investigate details, how your application might run out of space when allocating buffers for a newly opened file? You aren't at all clear about your question, and you leave us guessing about your software versions.

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