Debug - Aborting for one user but not another

ecclesr · Post by **ecclesr** » Tue Apr 18, 2006 4:18 pm

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

chulett · Post by **chulett** » Tue Apr 18, 2006 4:24 pm

First suggestion would be for the person with the issue to reinstall the client software and see if that helps.

ray.wurlod · Post by **ray.wurlod** » Tue Apr 18, 2006 6:58 pm

This is a known bug in 7.1 and later. Alas I don't have the ecase number, nor can I recall the particular circumstances under which it occurs.

ecclesr · Post by **ecclesr** » Tue Apr 18, 2006 10:16 pm

Thank you for your replies.

The developer in question has in the last month re install her DS client and reports that the issue with debug was present before and after the client was re installed.

Knowning that an ecase exists for this issue has renewed some of her faith

sb_akarmarkar · Post by **sb_akarmarkar** » Wed Apr 19, 2006 12:28 am

Hi,

I too got issue many time with debuging tool. I felt debuging tool is not much flexible in datastage. So i started my own way to degug job. By using constarint condition and sequential file. So i suggest dont let her lose her confidence try to find new way if wont work for us.

Thanks,
--Anupam

chulett · Post by **chulett** » Wed Apr 19, 2006 5:43 am

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.

sbass1 · Post by **sbass1** » Sun Mar 15, 2009 10:58 pm

Bump...

Does anyone know if IBM have issued a hotfix for this bug? I run into this issue ALL the time.

ray.wurlod · Post by **ray.wurlod** » Sun Mar 15, 2009 11:22 pm

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.

sbass1 · Post by **sbass1** » Mon Mar 16, 2009 12:49 am

Thanks for the Ray. But, as I saw you say in another post, this is a workaround, not a fix.

So, have IBM fixed this bug? Is it still an issue in 8.x?

ray.wurlod · Post by **ray.wurlod** » Mon Mar 16, 2009 2:27 am

I have experienced it in 8.1.