I was intrigued by the new RTT of socket inspector included in 11.0.3. Having recently updated, I decided to try it out.
On my test subject computer, it has multiple established socket connections both locally and externally. I can see them via netstat.
When I bring up debugger 11.0.3 and try out the suggested RTT inspector relevance it gave me some unexpected answers.
This is the relevance:
Q: ((ids of it, names of it) of processes of it, rtts of it) of sockets whose (tcp of it = True AND tcp state of it as string = "ESTABLISHED") of network
The answers Debugger provided were accurate for local socket to socket connections. What surprised me was that it didn’t displayed sockets established to remote systems. Is this intentional? Or am I missing something?
Bumping this post to see if anyone is familiar with how the new RTT inspector is supposed to work. Is it only for local sockets or remote ones as well?
Strange it seems to be working for me. Can you try this?
q: (local addresses of it, local ports of it, remote addresses of it, remote ports of it, rtt of it as string | "na", tcp state of it) of sockets whose (tcp of it and tcp state of it as string = "ESTABLISHED") of network
For me it’s showing the RTTs for loopback, inbound, and outbound connections.
OH it may have to do with looking up the processes. In the Fixlet Debugger’s default mode, where it’s running under your context, it can only lookup Processes that you own. So retrieving the process ID and Name is probably discarding results for all the processes that you don’t “own”.
Try running the Fixlet Debugger with “Evaluate → Local Client Mode”. That runs the query in client context and should have access to all the processes.