Re: Do you compile production programs for debug? -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Absolutely, we compile with debug. I am of the mindset that it should be
the IBM default for all of the compile commands. We have changed the
default value for all of the compile commands here.

- Dan

On Tue, Mar 31, 2015 at 2:44 PM, Dean Eshleman <Dean.Eshleman@xxxxxxxxxxxx>
wrote:

One of our developers asked why we don't compile our production programs
for debug. Their thought was, it would make it easier to debug a
production process when there was a problem. Currently, when we have a
production problem the developer tries to recreate it in a test
environment. If they can recreate it, they can debug it there. In the
rare circumstance they can't recreate it, we do recompile the program for
debug and put it into production. Currently, our developers do not have
authority to debug production jobs. A few admin types have this authority,
so it can be done.

Anyway, what do other people do. Do your production programs that you
write and use in house contain debug information? Are there any negative
side effects of doing that? Does it impact performance in any way? TIA

Dean Eshleman

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.