Sorry for the typo I meant that the debugger have recovery environment If the user code has errors
Sent from my iPhone On Apr 8, 2013, at 11:04 PM, Micheal Butz <[email protected]> wrote: > I think Dave is right about one thing > That a debugger have a debugging > Environment if the traceable code > Is faulty > > > Sent from my iPhone > > On Apr 8, 2013, at 10:57 PM, Ed Jaffe <[email protected]> wrote: > >> On 4/8/2013 6:47 PM, David Cole wrote: >>> WRT breakpoints, yes, 0C1s will occur when an address space, not involved >>> in the debugging session, attempts to execute a common storage breakpoint. >>> However, there are many simple techniques an XDC user can engage to make >>> this possibility either not occur or occur with vanishingly low probability. >> >> Not sure what others do, but I tend to use HOOK and/or TRACE instead of AT >> when working with common code and, of course, debug on a low-utilized shared >> or completely private system when possible. >> >> -- >> Edward E Jaffe >> Phoenix Software International, Inc >> 831 Parkview Drive North >> El Segundo, CA 90245 >> http://www.phoenixsoftware.com/ >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to [email protected] with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
