Method disconnectRequest

src/gdb.ts:1418–1448

(response: DebugProtocol.DisconnectResponse, args: DebugProtocol.DisconnectArguments)

    protected disconnectingPromise: Promise<void> = undefined;
    protected async disconnectRequest(response: DebugProtocol.DisconnectResponse, args: DebugProtocol.DisconnectArguments): Promise<void> {
        TcpPortScanner.PortAllocated.removeListener('allocated', this.tcpPortAllocatedListner);
        if (this.disconnectingPromise) {
            // One of the ways this happens when we have the following
            // * we are a child session of someone else
            // * the parent has already asked us to quit and in the process, we sent a TerminatedEvent to VSCode
            // * VSCode in turn asks to disconnect. all is good, we were quitting anyways. Not sure exactly what else we could do
            this.serverConsoleLog('Got disconnect request while we are already disconnecting');
            await this.disconnectingPromise;
            this.sendResponse(response);
            return Promise.resolve();
        } else {
            // We have a problem here. It is not clear in the case of managed life-cycles what the children are supposed to do.
            // If we try to wait for children to exit cleanly and then exit ourselves, we are having issues (when not in server mode
            // which is always the case for production).
            //
            // If we wait for a timeout or event and the child exits in the meantime, VSCode is killing the parent while we are still
            // not yet done terminating ourselves. So, let the children terminate and in the meantime, at the same time we terminate ourselves
            // What really happens is that when/if we terminate first, the server (if any) is killed and the children will automatically die
            // but not gracefully.
            //
            // We have a catchall exit handler defined in server.ts but hopefully, we can get rid of that
            //
            // Maybe longer term, what might be better is that we enter server mode ourselves. For another day
            if (this.args.chainedConfigurations?.enabled) {
                this.serverConsoleLog('Begin disconnectRequest children');
                this.sendEvent(new GenericCustomEvent('session-terminating', args));
            }
            return this.disconnectRequest2(response, args);
        }
    }

    protected async tryDeleteBreakpoints(): Promise<boolean> {
        try {