Repository navigation
Tags
Tags
Fix warn_if_stuck custom fun reporting the wrong process The custom report callback runs inside the spawned monitor process, so callers using format_stacktrace(self()) captured the monitor's (empty) stacktrace instead of the stuck process. Call the callback with the monitored pid when it accepts one argument; arity-0 callbacks keep working unchanged.