$ ./a.exe
EVALUATING from: 2010 1
.............To: 2010 361
Reading modis data...
Writing..modis.2010.daily
record number: 1

Program received signal SIGSEGV: Segmentation fault - invalid memory reference.

Backtrace for this error:
#0 0x53C872B1
#1 0x53D0BDCB
#2 0x61033A22
Segmentation fault (core dumped)

Did you compile with debug symbols enabled? You can run it under gdb to determine exactly where it blows up...

1 members found this post helpful.

Yeah, I also ran it under gdb, it also says as follows.
If any error can be solved, please let me know how to do...


shelly@hasegawa2 /cygdrive/e/WEB-DHM/MODIS/MODIS_data
$ gfortran -o a.exe server.f

shelly@hasegawa2 /cygdrive/e/WEB-DHM/MODIS/MODIS_data
$ gdb ./a.exe
GNU gdb (GDB) (Cygwin 7.10.1-1) 7.10.1
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-cygwin".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./a.exe...done.
(gdb) run
Starting program: /cygdrive/e/WEB-DHM/MODIS/MODIS_data/a.exe
[New Thread 5356.0x14e8]
[New Thread 5356.0x3cc]
[New Thread 5356.0x878]
[New Thread 5356.0xbdc]
EVALUATING from: 2010 1
.............To: 2010 361
Reading modis data...
Writing..modis.2010.daily
record number: 1

Program received signal SIGSEGV, Segmentation fault.
0x00401f40 in MAIN__ ()
(gdb)

Um, why are you posting Windows problems in a Linux forum?

What makes you think it's a Windows problem?

Edit: Ah, I see, because it's being run under cygwin.

A seg fault typically occurs when a program tries to write to memory that doesn't belong to it. It's usually caused by a program running past the end of an array or using memory locations before they've been allocated (or after they've been deallocated).

Since you haven't posted the source code, or even the name of the program or a link to it, I'm not sure what you expect us to do. Maybe contact the code provider?

1 members found this post helpful.