Skip to Content
Former Member
Mar 03, 2014 at 09:05 AM

Keeping break-point(?) in CL_HTTP_SERVER_NET->AUTHENTICATION



when testing a WD4A application, I often get something like a break-point in the specified method. There was no break-point set there, I can't deactivate it (once it does not exist) Tried logging-off, /$SYNC, did not help. Is there anything I can try to stop new session-windows with the new debugger coming up?

This is something that happens from time to time, sometimes the debugger opens and stops in a other place (also something like CL_HTTP*). Still it is in standard WD4A code, not customer.