NetNews Usenet Archive 1993 #3/NN_1993_3.iso/spool/comp/lang/fortran/5154

Internet Message Format | 1993-01-24 | 1.7 KB

Path: sparky!uunet!cs.utexas.edu!torn!news.ccs.queensu.ca!qucdn!matovicm
Organization: Queen's University at Kingston
Date: Sat, 23 Jan 1993 21:07:54 EST
From: <[e-mail]>
Message-ID: <[e-mail]>
Newsgroups: comp.lang.fortran
Subject: Re: dbx headache
References: <[e-mail]>
 <[e-mail]> <[e-mail]>
Lines: 22

Thanks a lot to all the people that bothered to respond. At least I know now
that my headache is real, because the responses seem to point somewhere in the
future (if FORTRAN lives long to see it?), with the exception of the dbx fea-
ture offered on the SPARC, but, then, I work on SGI for the time being.

I think I could have the solution in principle, but I couldn't make it work.
Here is the idea:
    DBX allows interactive function (and in FORTRAN, subroutine) calls from
within debugger, if this function/subroutine is linked with the program. This
way, I managed to incorporate a routine that dumps all my data in the output
files whenever a want it. I simply enter
       ccall mywrite
Than using other (simple) program I examine that database. This whole thing
would work MUCH better if I were able to pass the arguments to the subroutine
or function call. So far, I've been trying... The problem is that dbx requests
C calling conventions even for the FORTRAN debuging, and I couldn't match these
conventions so far. I've tried to reverse the order of arguments, to compile
the C routine (just the one to print data) using mkf2c interface, than assemb-
ler, and all I managed is to drive my frustration up. Anybody out there that
could add to this?

Darko Matovic