Skipping breakpoint when closing socket connection

[bjhilbrands]

Hi!

So I have been using a Unix sockets to interact with the debugger. Right now I made a rails controller that manages the interaction with the debugger, but in this workflow I do close the socket connection after each request and create a new one (Because instance variables do not persist between requests). The problem that I'm running into right now, is that it goes to the next breakpoint whenever the socket connection is closed.

For example, the controller receives a request to get the value of a certain variable, so it opens a socket connection, gets the value of the variable over the socket connection, and then closes the connection. It then receives the same request again, but now we are suddenly at the next breakpoint.

I was wondering if there is a particular reason for this behavior, and if anyone would perhaps know a way around this.

Thanks

[bjhilbrands]

Looking through the code, I found that the following code (Server.rb in the method readline) is seems to be responsible for this behaviour.

 input = (sock(skip: CONFIG[:skip_bp]) do |s|
        next unless s

        if @repl
          raise "not in subsession, but received: #{line.inspect}" unless @session.in_subsession?
          line = "input #{Process.pid}"
          DEBUGGER__.debug{ "send: #{line}" }
          s.puts line
        end
        sleep 0.01 until @q_msg
        @q_msg.pop.tap{|msg|
          DEBUGGER__.debug{ "readline: #{msg.inspect}" }
        }
      end || 'continue')

Just replacing the 'continue' with an empty string seems to result in the behavior that I want, but that does not really seem like a good solution.

[bjhilbrands]

It turns out I had to pass non-stop: true from my client to make this work, the above change did not actually achieve anything