`forkpty` calls `fork()` underneath. `fork()` in a multithreaded process is unsafe: only the calling thread survives in the child, but libc locks held by other threads remain "locked forever." With the multi-threaded Dart VM as parent, ~5% of spawns deadlocked in the child before `execve` (forensic probe: child stuck in S state with comm=`DartWorker`, master fd never sees POLLIN). `posix_spawn` uses `vfork` on glibc/musl/macOS, keeping the parent suspended until execve completes — no Dart code runs in the child. Pty pair built via the POSIX-standard `posix_openpt` / `grantpt` / `unlockpt` / `ptsname` sequence. Probed: zero hangs in 300 sequential spawns vs ~5% before. Behavior change: missing executable / missing workingDirectory now surface as a `PtyException` thrown by `NativePty.start` rather than a diagnostic written from the child to the slave PTY. Cleaner error path for callers. Side benefit: drops the `libutil.so.1` dynamic-library dependency. PTY now resolves entirely against libc via `DynamicLibrary.process()`. Splits the library-level `@Tags(['forkpty'])` on session_test.dart into a per-test tag, so the now-runnable-under-flutter-test cases contribute to coverage. `dart_test.yaml` declares the tag so the exclude-tags filters honor it. Drops the `retry: 2` workaround from the formerly-flaky registry test. D-5 amended. Trims session-introduced CHANGELOG entries that were over-verbose for the Keep-a-Changelog format. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
24 lines
840 B
Dart
24 lines
840 B
Dart
/// Error type for the PTY subsystem. Flutter-free — `dart:io`'s
|
|
/// `OSError` + `ProcessException` don't quite fit (we're a mix of
|
|
/// syscall-level and subprocess-level failures), and we can't pull
|
|
/// `PlatformException` from `package:flutter/services.dart` since the
|
|
/// core library stays Flutter-free per D-005.
|
|
library;
|
|
|
|
/// A PTY operation failed. [op] identifies the step (`posix_openpt`,
|
|
/// `posix_spawn`, `read`, `ioctl`, etc.); [errno] is POSIX errno when
|
|
/// the failure came from a syscall, otherwise `null`.
|
|
class PtyException implements Exception {
|
|
const PtyException(this.op, this.message, {this.errno});
|
|
|
|
final String op;
|
|
final String message;
|
|
final int? errno;
|
|
|
|
@override
|
|
String toString() {
|
|
final suffix = errno != null ? ' (errno=$errno)' : '';
|
|
return 'PtyException($op): $message$suffix';
|
|
}
|
|
}
|