AspertameMan wrote:
> Back in the 1970's when we ran fortran on an IBM machine we had this
> really powerful command called CALL FDUMP that if inserted into a
> program would send the names and values of every variable, at the time
> of its call, to a printer or file. [...]
This sounds like
Aspertame Man writes:
> After looking on the internet on the term "dumping core" I noticed that
> one had to write a piece of code to cause the crash.
Try looking for gcore.
Andreas.
--
Andreas Schwab, sch...@redhat.com
GPG Key fingerprint = D4E8 DBE3 3813 BB5D FA84 5EC7 45C6 250E 6F00 984E
> Simply building in a small standardized intrinsic function name to a
> common crash function that computer scientists might write to cause
> a core dump would make the compiler more user friendly to the non
> computer science crowd.
I'm confused. Why isn't "abort" the function that you want?
After looking on the internet on the term "dumping core" I noticed that
one had to write a piece of code to cause the crash.
I noted that one had to know what to do to cause the crash to get the
dump and gathered that while computer scientists and most engineers know
how to do this, it is not so ob
Quoting Aspertame Man :
Back in the 1970's when we ran fortran on an IBM machine we had this
really powerful command called CALL FDUMP that if inserted into a
program would send the names and values of every variable, at the time
of its call, to a printer or file. In my opinion this was muc
On Sun, 05 Dec 2010 14:30:40 -0600
Aspertame Man wrote:
>
> Back in the 1970's when we ran fortran on an IBM machine we had this
> really powerful command called CALL FDUMP that if inserted into a
> program would send the names and values of every variable, at the time
> of its call, to a pr
