Problem getting gfortran signal implementation to work (MingW64 4.5.1)

Steve Kargl sgk@troutmask.apl.washington.edu
Fri May 6 20:05:00 GMT 2011


On Fri, May 06, 2011 at 10:47:34PM +0300, Janne Blomqvist wrote:
> On Fri, May 6, 2011 at 20:24, Steve Kargl
> <sgk@troutmask.apl.washington.edu> wrote:
> > I do however suspect that when -fbacktrace came
> > into being that the expectation was that other
> > OSs would implement GLIBC's backtrace() function.
> 
> Looking at the code, if GLIBC backtrace() is not available, it tries
> to use the pstack utility which should be available at least on
> Solaris, and according to Google FreeBSD also has it.
> 

Hmmm.  It seems that pstack is available in FreeBSD's
port collection.  I never know that!

troutmask:kargl[209] more /usr/ports/sysutils/pstack/pkg-descr
"pstack" is a workalike for the Solaris program of the same name.
Running pstack on a process or core file produces a stack trace of
each thread in that process.  Unfortnately, it appears to be
i386-centric

% sudo portmaster sysutil/pstack
...
===>  pstack-1.2_1 is only for i386, while you are running amd64.
*** Error code 1

troutmask:sgk[217] gfc4x -o z -fbacktrace -ffpe-trap=invalid,zero yt.f90
troutmask:sgk[218] ./z
 setting up signal handler
 hello again
STOP abexit stop

It at this point, that I think one might anticipate see
Warning: backtrace facility unavailable.

-- 
Steve



More information about the Fortran mailing list