Looking closer, it's clearly a problem with the way Debugger processes the thread's call-stack. Somehow it removes the current function frame from the stack on stepping (`doSomeThing < start_thread < clone`). This triggers the UI to process the next item in the stack (`start_thread`), so it tries to load the source for that frame.Looks like his plugin needs a deep dive to fix this, or at least to figure out what's going on. At least there's a test case, which is a good thing.
-- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/issues/1069#issuecomment-817244052
