douchuza8908 2015-02-24 08:52
浏览 188


I have a process written in golang that runs as a daemon.

After a few days it stops producing output with no apparent reason. I think it might be an internal deadlock. If I do a strace -p <PID> I can see the line

futex(0x9aaba0, FUTEX_WAIT, 0, NULL

and apparently that call never ends. I would like to use the already running process (since I don't know how/when to trigger the bug again) to debug the problem.

How can I see what goroutines are running and where they? How can I dump from the process whatever other information might be useful to debug the problem?

  • 写回答

1条回答 默认 最新

  • doulin2025 2015-02-24 15:21

    You can send any go program a QUIT signal, and it will exit with a full stack trace, showing the state of all goroutines, and how they are blocked.

    As for strace, go programs are always multithreaded, so you always need to add the -f option

    本回答被题主选为最佳回答 , 对您是否有帮助呢?



  • ¥15 微信公众号如何开发网页
  • ¥15 h3.6m 人类行为预测论文复现
  • ¥50 wordpress项目注册报失败刷新后其实是成功状态,请求排查原因
  • ¥20 linxu服务器僵尸进程不释放,代码如何修改?
  • ¥15 pycharm激活不成功
  • ¥40 如果update 一个列名为参数的value
  • ¥15 基于51单片机的水位检测系统设计中LCD1602一直不显示
  • ¥15 OCS2安装出现问题,请大家给点意见
  • ¥15 ros小车启动launch文件报错
  • ¥15 vs2015到期想登陆但是登陆不上