Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Debugger keeps popping up

andre_kster
Explorer
0 Likes
2,236

Hello everyone,

I keep having problems with the new debugger in a Netweaver 7.0

Sometimes, I have no clue by which rule, I can not properly leave the debugger. I press F8 when debugging my code to leave the debugger. After this each time I save my coding or try to activate I end up in the debugger again, right in the middle of some SAP coding. Only remedy I found so far is to log out and log in again. Restarting the transaction (/nse80) is not working.

To state the obvious:

- I have no break-points in the code I end up in

- I tried /hx to detach the debugger

Has anyone else experienced this? Is there a note somewhere out there?

Regards

Andre

1 ACCEPTED SOLUTION
Read only

naveen_inuganti2
Active Contributor
0 Likes
2,111

Hi..,

Check..

Some body using the same logon details.

Thanks,

Naveen.I

13 REPLIES 13
Read only

naveen_inuganti2
Active Contributor
0 Likes
2,112

Hi..,

Check..

Some body using the same logon details.

Thanks,

Naveen.I

Read only

0 Likes
2,111

SM04 looks OK, didn't give out my password anyway.

Read only

0 Likes
2,111

Ok cool its fine.

And check if there are any static break points in that code i.e. with syntax BREAK-POINT, and then report to basis guys once.

Thanks,

Naveen.I

Read only

0 Likes
2,111

No static or user dependant break points either.

Maybe it is this other type of breakpoit which causes the system to stop at the next piece of code, you know, the one that is used when you press 'Debugging' when F8-testing a method for example.

Next time I will have a look at the callstack.

Read only

0 Likes
2,111

Check whether your patch level for Gui needs to be >= 3.

a®

Read only

0 Likes
2,111

Oh, I hope it is not the LogOn, I have no influence on that as I work in a customer's Citrix environment.

They are still using a 620 Logon, Patch Level 66.

We tried for some time to get them to update, we are currently undergoing a large development project for them and the 620 does not yet support the new editor

Read only

0 Likes
2,111

Yes some of the user of ours also using Citrix had this problem,

But if you are using 710 Final Release then you can avoid

a®

Read only

0 Likes
2,111

As I said, the customer is not willing to upgrade the Logon on the Citrix, at least not for the next months.

After getting used to the new editor with its syntax highlighting and auto completion the old new editor is quite disappointing.

Anyway, I will not complain, the R/3 in the background is a 4.5, back to the line editor down there...

Read only

0 Likes
2,111

After upgrading to 710 release then also you use old editor ie in the se38> utilities> settings> abapeditor> editor-->select the "frontend editor (old)

a®

Read only

0 Likes
2,111

> As I said, the customer is not willing to upgrade the Logon on the Citrix, at least not for the next months....

That is a shame, as it will now take longer for the code to be developed, and therefore cost them more...

Read only

Former Member
0 Likes
2,111

Thats strange, One more obvious that you might have missed:

Have you turned on Update or system debugging? Check in the debugger settings.

Read only

0 Likes
2,111

System debugging is off, update debugging was switched on. I deselected it, although i do not see a connection to the behaviour.

I'll wait and see if it helps, currently I do not have the problem as i relogged, hopefully it stays this way

Read only

naimesh_patel
Active Contributor
0 Likes
2,111

There might be some assertion breakpoint active.

Check in SAAB transaction.

Regards,

Naimesh Patel