According to Wikipedia:
“In 1946, when Grace Hopper was released from active duty, she joined the Harvard Faculty at the Computation Laboratory where she continued her work on the Mark II and Mark III computer systems. Operators traced an error in the Mark II to a moth trapped in a relay, coining the term bug. This bug was carefully removed and taped to the log book. Stemming from the first bug, today we call errors or glitches in a program a bug.”
In our environment, we may not have to deal with moths but sadly developers still have to deal with bugs, some big, some small. The real challenge is discovering why the system is behaving incorrectly and fixing it.
So how do you identify a bug, replicate it, and most importantly analyze the cause of the problem so that you can either correct the problem or determine a workaround and make sure it works?
Systems and the environments they are running in are getting more and more complex so many of the old techniques that used to resolve problems are no longer practical. Running applications on the web or as background services limits one’s ability to debug applications. Worse yet, many applications need to be available 24/7 meaning you are going to have to solve problems on a live system while users continue to access the application.
This year, at DireXions 2017, we have an entire session dedicated to helping you find and correct problems in your application. Some of the topics that we will be discussing are:
- Using the Windows Trace and debug windows
- Debugging iNomads/Web applications
- Using the PxPlus debugging tools in IT and the DBG command
- Understanding the enhanced Dump web page
- Looking at the system journal
- Adding application debug logic with minimal performance impact
- Reviewing system crashes and what can cause them
Join us at this exciting session where we guarantee a Moth Free environment on the High Seas.