← Back to AI Insights
Gemini Executive Synthesis

dsh-Go local engine execution within containerized Android/HarmonyOS environments.

Technical Positioning
Reliable and performant local execution of the DSH engine across diverse mobile operating systems and containerization layers. Accurate error diagnostics and user guidance.
SaaS Insight & Market Implications
This bug report reveals a critical failure in dsh-Go's core local engine functionality within specific, yet significant, mobile environments (HarmonyOS + container). The `getcwd ENOSYS` and `exec EFAULT` errors strongly suggest underlying system call interception issues, likely due to the `proot` environment clashing with the host container's security or virtualization layers. This is not a minor bug; it's a fundamental architectural incompatibility preventing the product from operating as advertised on certain devices. The generic "low memory" error message further exacerbates the developer pain point by misdirecting troubleshooting efforts. For a B2B SaaS, such deep-seated compatibility issues on major platforms like HarmonyOS represent a significant market barrier, limiting addressable market and eroding trust in the product's robustness and reliability. Clear compatibility documentation and intelligent error handling are imperative.
Proprietary Technical Taxonomy
本地引擎 鸿蒙 7 卓易通 Anco/LXC 容器 getcwd ENOSYS exec EFAULT proot ptrace

Raw Developer Origin & Technical Request

Source Icon GitHub Issue Oct 25, 2026
Repo: ccch1mneyyy/dsh-Go
[Bug] 鸿蒙 7 + 卓易通:本地引擎无法启动(getcwd ENOSYS / exec EFAULT)

## 环境

华为 Pura X Max,HarmonyOS 7.0.0.109(OpenHarmony 7.0.0.105,API 26)。

dsh-go 装在卓易通里跑(`com.zhuoyi.browser`,底层是 Anco/LXC 容器),包名 `io.github.ccch1mneyyy.dsh_app`。0.9.1 的时候就这样,升到 0.9.3 没变。

## 现象

App 能打开,界面正常,但引擎从来没连上过。顶部一直显示「新对话 · 未连接」,中间是「夜深了 / 引擎未连接」,输入框发不出消息。

卡片上给的说法是「引擎被系统结束了,多半是内存不足或系统省电」。点重试没有变化,重装也一样。

## 日志

查看日志里只有两行:

```
sh: 0: getcwd() failed: Function not implemented
/bin/sh: 1: exec: /usr/local/bin/dsh: Bad address
```

## 我试过的

前台启动是这个错,切后台待 5 分钟还是这个错,锁屏 5 分钟也一样。清内存、重启应用、重试都试过,没有变化。

用 hdc 挂了 10 分钟监控(159 次采样):App 的 mission 大部分时间都在,前后台切换正常,引擎的错误从启动起就存在。期间只出现过一次进程被销毁(00:43:36 消失,4 秒后重建,可用内存从 3.01 GB 跳到 3.92 GB)。所以内存回收确实会发生,但不是这次的根因,因为引擎在销毁之前就已经起不来了。

## 补充证据

拆了 0.9.3 的安装包看 `assets/runtime/manifest.json`:rootfs 是 `rootfs-arm64-v8a.tar.xz`(原生 arm64,没有 x86 模拟层),引擎由 termux 版 proot 5.1.107.98 启动,`launch.env` 里只有 `PROOT_LOADER`、`PROOT_TMP_DIR`、`PROOT_L2S_DIR`、`LD_LIBRARY_PATH`,没有 `PROOT_NO_SECCOMP`。

完整的启动参数和对错因的对应关系写在下面的评论里。

## 我的猜测

`getcwd` 返回 ENOSYS,正常 Linux 不会这样;`execve` 返回 EFAULT,说明二进制没真正加载。两个凑一起,像是 proot 对系统调用的拦截被宿主容器限制住了。proot 依赖 ptrace 和 seccomp,这类调用一旦被挡,表现就是现在这样。

## 希望

一是启动失败时把真实错误报出来,和「运行中被系统结束」分开,别都用「内存不足」兜底。

二是检测到环境不支持时,直接引导到远程主机模式,而不是让用户去清内存。

三是 README 里标一下兼容性,比如真机 Android、模拟器、鸿蒙加容器分别是什么情况,后面的人能少走点弯路。

Developer Debate & Comments

No active discussions extracted for this entry yet.

Adjacent Repository Pain Points

Other highly discussed features and pain points extracted from ccch1mneyyy/dsh-Go.

Extracted Positioning
Remote console user interface rendering, specifically the input composer, within dsh-Go's WebView.
Seamless and fully functional remote interaction experience, ensuring all UI elements are correctly rendered and accessible.
Extracted Positioning
Workspace management and historical conversation organization within dsh-Go.
Intuitive and efficient user experience for managing conversational context and project-specific data. Data integrity and user control over information architecture.
Extracted Positioning
dsh-Go mobile application installation.
Ensuring mobile application integrity and compatibility with OEM Android distributions (ColorOS).

Frequently Asked Questions

Market intelligence mapped to dsh-Go local engine execution within containerized Android/HarmonyOS environments..

What problem does dsh-Go local engine execution within containerized Android/HarmonyOS environments. solve?
Based on our AI analysis of the original developer request, its primary technical positioning is: Reliable and performant local execution of the DSH engine across diverse mobile operating systems and containerization layers. Accurate error diagnostics and user guidance.
What is the general sentiment around dsh-Go local engine execution within containerized Android/HarmonyOS environments.?
Yes, we have tracked 2 direct responses and active debates regarding this specific topic originating from GitHub Issue.
What are the foundational technologies related to dsh-Go local engine execution within containerized Android/HarmonyOS environments.?
Our proprietary extraction maps dsh-Go local engine execution within containerized Android/HarmonyOS environments. to adjacent architectural concepts including 本地引擎, 鸿蒙 7, 卓易通, Anco/LXC 容器.

Engagement Signals

2
Replies
open
Issue Status

Cross-Market Term Frequency

Counts stored text matches for foundational terms like seccomp and 兼容性 in analysed public discussions. These counts do not measure adoption.

Stored text matches, not adoption or market-share measurements.

  • seccomp: 4 records
  • 兼容性: 2 records
  • 本地引擎: 1 records
  • 鸿蒙 7: 1 records
  • 卓易通: 1 records
  • Anco/LXC 容器: 1 records
  • getcwd ENOSYS: 1 records
  • exec EFAULT: 1 records
  • proot: 1 records
  • ptrace: 1 records
  • 系统调用拦截: 1 records
  • 远程主机模式: 1 records