[Info-vax] fortran version && Compile the main file in debug mode only

[HCorte]

A sexta-feira, 14 de agosto de 2020 à(s) 20:46:34 UTC+1, Stephen Hoffman escreveu:
> On 2020-08-14 15:01:34 +0000, HCorte said: 
> 
> > The why not compile everthing with debug is that some of the 
> > dependecies may be in use by other programs and don't know whant would 
> > be implications if there would be any... but know that you asked you 
> > are right the other programs were compile and linked without the /DEBUG 
> > flag at the time so it wouldn't interfere now.
> I'd think that'd be a form of premature optimization. Try the build and 
> see, and check for the performance difference for your particular app, 
> if you prefer praxis. 
> 
> Build it all with /DEBUG /NOOPTIMIZE. Debugging and disabling the 
> optimizer does make the code somewhat slower, though typically not 
> significantly slower, and /DEBUG /NOOPTIMIZE doesn't usually effect the 
> app otherwise. 
> 
> "Usually"? If the app behavior does change with the debugger, the app 
> is usually broken. There's usually a stack corruption or timing bug or 
> some other latent app bug. 
> 
> What you're headed for with your current approach here is more "fun" 
> when you find the need to step into or otherwise poke around in object 
> code not built /DEBUG /NOOPTIMIZE. 
> 
> And you're going to be operating with your own side-built objects or 
> side-built object library anyway, so the whole discussion there is 
> seemingly moot. You're not effecting anyone else, here. 
> 
> The newest OpenVMS Fortran compiler is Fortran 95. The Flang compiler 
> might appear on OpenVMS x86-64, but that's unlikely to arrive on older 
> platforms, and not arriving on your schedule. For comparison, the 
> newest C on OpenVMS is ~C99. 
> 
> BTW: you'll want to learn about listings with machine code, and a full 
> linker map, as that's the means to debug an app crash back to the 
> associated source code, when working with /NODEBUG /OPTIMIZE. 
> 
> BTW: an app can launch the debugger on itself, and can pass commands 
> and can script the debugging. Which can be a means to add logging and 
> related debugging into an app. 
> 
> BTW: Documentation resources: OpenVMS Fortran User's Guide, OpenVMS 
> Programming Concepts Manual, OpenVMS User's Manual, Fortran Language 
> Reference Manual. All are posted around the 'net. 
> 
> 
> -- 
> Pure Personal Opinion | HoffmanLabs LLC
   
Thanks for the feedback, 
 
Hoff about an app can lauch the debugger on itself, was reading the 1.7 Starting the Debugger After Interrupting a Running Program of https://vmssoftware.com/pdfs/HP_branded_docs_1st_batch/HP_OpenVMS_Debugger.pdf but isn't what you refered and also interest to use can you point to the correct documentation?

Have a program that created and run using a "cron job" well not realy a cron job since not using a scheduler but the dcl submit with after: 
            > submit/LOG_FILE=DKD10:[path]/NOPRINTER/after="+:1" runswap.com

where the COMMAND PROCEDURE runswap is only the dcl command run a exe
   > type runswap.com
   $RUN DKD10:[path]SWAP.EXE
   $EXIT

where SWAP.EXE using the SUBMIT to simulate a program that is alls running and wanted to make it call the debugger as you refered in the code how to achieve that and in what documentation talks or refers that??