You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
OpenHarmony: csc exits with SIGSEGV (139) compiling a 1.27MB source file #2
DOTNET_TieredPGO=0rc=0 dll=yes
(3/3 success, no code 139)
Same flags inside the runner (prebuilt_826=false, run 44503217746): still csc ... code 139 once, run failed.
So the analyzer pass over the 1.27MB source raises the failure rate but the crash is not specific to it; the crash remains intermittent and environment-dependent (runs 4x green / then all-red).
Triage capability check: crash dumps are not produced on this port.
$ DOTNET_DbgEnableMiniDump=1 DOTNET_DbgMiniDumpType=2 DOTNET_DbgMiniDumpName=.../core.%p dotnet t.dll
run rc=134 # SIGABRT from the unhandled exception
$ ls dumps
(empty) # no dump written
createdump exists next to the runtime (shared/Microsoft.NETCore.App/11.0.0/createdump), but it only dumps its own parent (createdump --help: "createdump writes a dump of its parent process; a target PID cannot be specified"), so it cannot be used to capture a csc crash.
Consequence: there is no supported way to get a native stack for the SIGSEGV on this host. Root-causing #2 will need either
a dump-capable build of the port (pid-taking createdump), or
reproducing on a host with a debugger (lldb/gdb + SOS) available.
Until then the mitigation stands: run the suite from a prebuilt assembly (prebuilt_826=true).
pid-taking createdump (a cross-process attach) cannot work here, which explains why this port only dumps its own parent: createdump is forked by the crashing process, and a child attaching to its parent is permitted while attaching to an unrelated pid is not.
lldb/gdb attach is equally blocked (no debugger installed either).
So the only in-process option left is the runtime's own crash path. That path is also suspicious: with
an unhandled exception aborts the process (rc=134) but no dump file is written, even though createdump exists next to the runtime. Worth checking whether the runtime was built with createdump support (CLR_CMAKE_ENABLE_CREATEDUMP) and whether the env-var plumbing reaches createdump on this port.
Next feasible step: instrument the runtime (stress log) since it is in-process and does not need ptrace.
Conclusion: root-causing this crash requires a supported build host (Linux glibc x64/arm64) to produce a runtime with FeatureStressLog=true (or a dump-capable createdump), then deploy that runtime back to the device. On the device itself only the mitigation path is available (prebuilt assembly, prebuilt_826=true).
Activity
springmin commentedon Nov 19, 2026
More data: disabling analyzers helps but does not eliminate it.
bin,/p:RunAnalyzers=false /p:TreatWarningsAsErrors=false:rc=0 dll=yesDOTNET_ReadyToRun=0rc=0 dll=yesDOTNET_TieredPGO=0rc=0 dll=yes(3/3 success, no
code 139)prebuilt_826=false, run44503217746): stillcsc ... code 139once, run failed.So the analyzer pass over the 1.27MB source raises the failure rate but the crash is not specific to it; the crash remains intermittent and environment-dependent (runs 4x green / then all-red).
springmin commentedon Nov 19, 2026
Triage capability check: crash dumps are not produced on this port.
createdumpexists next to the runtime (shared/Microsoft.NETCore.App/11.0.0/createdump), but it only dumps its own parent (createdump --help: "createdump writes a dump of its parent process; a target PID cannot be specified"), so it cannot be used to capture acsccrash.Consequence: there is no supported way to get a native stack for the SIGSEGV on this host. Root-causing #2 will need either
lldb/gdb+ SOS) available.Until then the mitigation stands: run the suite from a prebuilt assembly (
prebuilt_826=true).springmin commentedon Nov 19, 2026
Route check:
ptraceis denied by the sandbox, so external dump/debugger routes are out.Implications:
createdump(a cross-process attach) cannot work here, which explains why this port only dumps its own parent:createdumpis forked by the crashing process, and a child attaching to its parent is permitted while attaching to an unrelated pid is not.So the only in-process option left is the runtime's own crash path. That path is also suspicious: with
an unhandled exception aborts the process (
rc=134) but no dump file is written, even thoughcreatedumpexists next to the runtime. Worth checking whether the runtime was built with createdump support (CLR_CMAKE_ENABLE_CREATEDUMP) and whether the env-var plumbing reachescreatedumpon this port.Next feasible step: instrument the runtime (stress log) since it is in-process and does not need ptrace.
springmin commentedon Nov 19, 2026
Route 3 check: the repo cannot build its own runtime on this host.
So
build.sh(Arcade) refuses to run on HarmonyOS, which means the stress-log variant of the runtime cannot be produced here either.Status of all triage routes on this host:
createdump— blocked:ptracereturns EPERM for non-descendant pids.build.shrejects the HarmonyOS host.Conclusion: root-causing this crash requires a supported build host (Linux glibc x64/arm64) to produce a runtime with
FeatureStressLog=true(or a dump-capable createdump), then deploy that runtime back to the device. On the device itself only the mitigation path is available (prebuilt assembly,prebuilt_826=true).