Forum Post: RE: Structured error handling and debugging

  • Thread starter Thread starter Peter Judge
  • Start date Start date
Status
Not open for further replies.
P

Peter Judge

Guest
That sounds like a useful idea. You can – as an alternative or workaround – set a breakpoint on error (any or any number). From memory, you can do this in the Breakpoints view in the Debug perspective. This will effectively do what you want (ie stop execution when the error occurs and keep program/stack state). -- peter From: Stefan Drissen [mailto:bounce-14941@community.progress.com] Sent: Thursday, 13 March, 2014 08:16 To: TU.OE.Development@community.progress.com Subject: RE: Structured error handling and debugging RE: Structured error handling and debugging Reply by Stefan Drissen No, I mean being able to view the entire state including all locally scoped variables, input output parameters, scoped buffers etc. Ideally the debugger should be able to stop between the error and the error being caught. Stop receiving emails on this subject. Flag this post as spam/abuse.

Continue reading...
 
Status
Not open for further replies.
Back
Top