Nostr Web Client

Debuggers are way more efficient at manipulating points to print variables etc though.

You can also do profiling and see which threads/mutexes/functions are introducing problems and then step through those with a debgugger.

mleku 2y ago

doesn't work in a sub-100ms timescale.

when someone makes a debugger that makes this kind of state inspection post mortem i'll be using it. it's simply impractical for especially low latency network protocols, the debugger assumes linearity and single threaded execution. even the Go debugger, delve is like this, despite most Go code being highly concurrent and parallel and time sensitive.

Reply to this note

Please Login to reply.

Discussion

mleku 2y ago

it's not just the inspection though, because very often timeouts are too short to tolerate the general slowdown of having compiled it to be debugged.

gsovereignty 2y ago

Yeah, valid point, I always have to use a workaround for network calls etc