We deliver all production code with Debug, as there is very little security risk in doing so, and the benefits, when needed, are huge.
This isn't the 1990s, when processor, memory, and DSAD resources were slim. (grin)
-Paul
On Apr 01, 2015, at 12:17 AM, Birgitta Hauser <Hauser@xxxxxxxxxxxxxxx> wrote:
I'm working for a small software house and for me it's a huge problem that
our programs are delivered without debug.
Independent how good your programs are tested there are always customers
with "special" data and "special" situations.
Instead of simply starting a team viewer session and debugging the program
on the customer's machine with "live" data in the problematic situation, we
need to try to rebuild the situation in our test environment, which may take
a bunch of time and even after we are still not sure if we could reconstruct
the problematic situation.
... IMHO it's a huge waste of time.
I'd beg my manager would allow we can deliver our programs with debug
(beginning with 6.1 it is even possible to secure debugging with a
password!)
Mit freundlichen Grüßen / Best regards
Birgitta Hauser
"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
-----Ursprüngliche Nachricht-----
Von: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von Dean
Eshleman
Gesendet: Tuesday, 31.3 2015 20:44
An: Midrange-L Mailing list xxxx
Betreff: Do you compile production programs for debug?
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.
midrange.com
