This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug fortran/70058] Segmentation fault when open file with existing file and status = "UNKNOWN"


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70058

--- Comment #7 from kargl at gcc dot gnu.org ---
(In reply to Jerry DeLisle from comment #6)
> (In reply to kargl from comment #5)
> > (In reply to Jerry DeLisle from comment #4)
> > > The problem does not exist on Linux for sure.  Not sure if this is a TDM
> > > distribution problem, a Windows problem, a MingW problem, or gfortran.
> > > 
> > > I am going to have to get set up on Windows so this may take a while.
> > 
> > From the backtrace in comment #3,
> > 
> > (gdb) backtrace
> > #0 in strcmp () from C:\WINDOWS\system32\msvcrt.dll
> > #1 in libgfortran_64-3!clog10l ()
> > #2 in libgfortran_64-3!clog10l ()
> > #3 in libgfortran_64-3!_gfortran_unpack1_char4 () 
> > #4 in libgfortran_64-3!_gfortran_unpack1_char4 ()
> > #5 in libgfortran_64-3!_gfortran_st_open ()
> > 
> > I doubt that this is a gfortran problem.  It is highly unlikely that
> > OPEN uses a complex*16 log10 function that calls itself.
> 
> No kidding Steve. This could be linking against the wrong library. Another
> possibility I suppose is memory corruption and the prgram is jumping into
> never never land. We do not really no the creators of or the integrity of
> the TDM distribution. Out of curiosity I am going to try to set it up in a
> sandbox and see what I can find.

TDM is 2+ releases behind.  Don't waste your time.  Paul should 
report the problem to TDM or install a newer version of gfortran

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]