Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Show information while downloading debug symbols

未关闭
#263 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
45/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
cpp, python
领域
cli, devtools

调研方向

首先跟踪 pystack 的调试符号下载路径,并针对需要大型符号的进程运行它,例如使用 QtWebEngine 或 Chromium 的进程。完成的标准是,用户能在等待之前或等待期间看到清晰的下载状态消息(如果可行则显示进度),并能判断是什么在消耗时间或数据。

由索引模型根据 Issue 内容生成。

描述

enhancement
Is there an existing proposal for this?
  • I have searched the existing proposals
Is your feature request related to a problem?

I tried pystack the first time, in a somewhat mediocre WiFi (capped to 20 MBit/s; I assume there are parts of the world where way less than that is common for many people). I used it on a project which has a lot of C++ debug symbols (via QtWebEngine/Chromium).

Given the claims about performance in the readme, I was quite surprised when pystack only printed basic information (up to "The process died due receiving signal SIGSEGV"), and then hung for 3.5 minutes before printing a stack.

Only while investigating the issue, I figured out the culprit was downloading of a couple 100MB of debug information (if it's any indication, my ~/.cache/debuginfod_client/ is currently 1.7 GB), and printing of the stack was indeed lightning fast! 🚀

As an additional consideration, I'm often on metered networks (tethering via a mobile connection while abroad). With that, such a message would have made me realize what was going on so I could cancel the download before it burns all through my data.

Describe the solution you'd like

At minimum, a "Downloading debug information..." would have helped here already. Ideally, some live updating progress like "Downloading debug information for libXYZ.so (1MB/100MB)" or somesuch would be even better.

Alternatives you considered

Running pystack on pystack to realize why it was hanging 😉

主要语言
C++
星标
1.2k
派生
74
平均合并
1 天 6 小时
30 天内合并 PR
11

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

bloomberg/pystack 的其他 Issue

查看 bloomberg/pystack 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。