Re: Do you compile production programs for debug?

My .02...

Compile with debug info. The only "cost" I'm aware of is a larger object.

But programmers shouldn't normally have authority to debug in production.

They should however, have some way to get the authority when needed.

Charles

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
Software Development Architect

Everence Financial
1110 North Main Street
PO Box 483
Goshen, IN 46527
Phone: (574) 533-9515 x3528
www.everence.com<http://www.everence.com/>

______________________________________________________________________
Confidentiality Notice: This information is intended only for the
individual or entity named. If you are not the intended recipient, do not
use or disclose this information. If you received this e-mail in error,
please delete or otherwise destroy it and contact us at (800) 348-7468 so
we can take steps to avoid such transmission errors in the future. Thank
you.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.