Debug - Aborting for one user but not another
Moderators: chulett, rschirm, roy
Debug - Aborting for one user but not another
Hi
One of our developers - every time they add break points and run debug sessions their jobs abort.
Yesterday I ran debug for a job that the developer had previously tried to debug with same break point - their debug session aborted , my was able to be debugged without issue.
The developer is losing her confidence and avoids using debug
Has anyone had this similar situation - is there a reason for this
Thanking you all in advance
One of our developers - every time they add break points and run debug sessions their jobs abort.
Yesterday I ran debug for a job that the developer had previously tried to debug with same break point - their debug session aborted , my was able to be debugged without issue.
The developer is losing her confidence and avoids using debug
Has anyone had this similar situation - is there a reason for this
Thanking you all in advance
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 232
- Joined: Fri Sep 30, 2005 4:52 am
- Contact:
Another suggestion would be to always debug from a 'fresh' Designer session. I've had intermittent issues if I've been working with a job or several jobs for a period of time in a Designer session and then attempt to debug. It usually results in a crash or the more typical abort with the 'debugging client has disconnected' error.
I've found that if I start a new Designer session and then open and debug a job before doing enything else in that session it generally goes much much better.
I've found that if I start a new Designer session and then open and debug a job before doing enything else in that session it generally goes much much better.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Close the job, re-open it, re-compile with your breakpoints enabled. If you're really paranoid, close and re-open it again and you probably won't get "debugger client has disconnected" aborts.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact: