06-14-2007 5:48 PM
Hi-
I am facing problem with the new debugger in ECC 6.0.
When I leave the debugger on in the middle and leave the debugger window idle for some time, the window gets stuck.
Can anyone of you know how to avoid this problem??
Thanks.
Ramesh.
09-12-2007 3:25 PM
Hi,
The simple reason for the new debugger to behave like this is that it opens up a new ACTIVE session which is active always unless you totaly come out of the program even out of the list display.
Cheers
VJ
06-14-2007 6:02 PM
Hi,
I think this is a known problem. This happens also, when your program creates a list and you are still in the list display. Leave the list display and thus the program an the window will be freed.
I avoid the problem by using the old debugger - Still I do not see real advantage in using new debugger.
Regards,
Clemens
09-12-2007 2:57 PM
09-12-2007 3:22 PM
I have found a number of advantages to the new debugger. Couple of simple ones are:
Because it does not force a commit work on the transaction being debugged it shows a true picture of what is happening. For example - debug HR PA30 infotype with dynamic action (I think) to update a second infotype - old debugger prevents the second update from occuring, but it can be debugged in new one.
New debugger also allows better display of long field values
I just close the extra debug window using the sapgui stop transaction option when done with it.
Andrew
09-12-2007 3:25 PM
Hi,
The simple reason for the new debugger to behave like this is that it opens up a new ACTIVE session which is active always unless you totaly come out of the program even out of the list display.
Cheers
VJ
09-13-2007 8:20 AM
Just enter /hx in the session that started the debugger, then it will go away.