option to not override signal handler

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

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
python
领域
backend

调研方向

从 ipykernel/kernelbase.py 中的 pre_handler_hook 开始,跟踪 dispatch_shell 如何调用它。确定嵌入应用程序如何选择不替换其 SIGINT 处理程序,然后验证自定义处理程序仍保持不变,同时内核的正常信号处理仍能正常工作。

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

描述

See also https://github.com/jupyter/qtconsole/issues/490

Hey there,

how can I embed qtconsole into an application without it overriding my own application's custom sigint handler?

Assume you have code that does

    std::signal(SIGINT, &handleSigInt);
    ...
    // do not initialize signal handlers
    const auto initsigs = 0;
    Py_InitializeEx(initsigs);

Then it is embedding qtconsole eventually, but at that point the sigint handler will be unset:

Thread 1 "QiTissue" hit Breakpoint 3, __interceptor_sigaction (signum=2, act=0x7fffffff8a60, oldact=0x7fffffff8b00)
    at /build/gcc/src/gcc/libsanitizer/sanitizer_common/sanitizer_signal_interceptors.inc:55
55      in /build/gcc/src/gcc/libsanitizer/sanitizer_common/sanitizer_signal_interceptors.inc
(gdb) bt
#0  __interceptor_sigaction(int, __sanitizer::__sanitizer_sigaction const*, __sanitizer::__sanitizer_sigaction*)
    (signum=2, act=0x7fffffff8a60, oldact=0x7fffffff8b00)
    at /build/gcc/src/gcc/libsanitizer/sanitizer_common/sanitizer_signal_interceptors.inc:55
#1  0x00007fff5c055f0f in PyOS_setsig (sig=sig@entry=2, handler=handler@entry=0x7fff5c0b6fec <signal_handler>)
    at Python/pylifecycle.c:2536
#2  0x00007fff5c0b849f in signal_signal_impl
    (module=<optimized out>, handler=<built-in method default_int_handler of module object at remote 0x7fff51eeaa40>, signalnum=2) at ./Modules/signalmodule.c:505
#3  signal_signal (module=<optimized out>, args=<optimized out>, nargs=<optimized out>)
    at ./Modules/clinic/signalmodule.c.h:141
#4  0x00007fff5bf7bbf8 in cfunction_vectorcall_FASTCALL
    (func=<built-in method signal of module object at remote 0x7fff51eeaa40>, args=0x7fff58a24a88, nargsf=<optimized out>, kwnames=<optimized out>) at Objects/methodobject.c:426

or in python terms:

(gdb) py-bt
Traceback (most recent call first):
  <built-in method signal of module object at remote 0x7fff51eeaa40>
  File "/usr/lib/python3.9/signal.py", line 47, in signal
    handler = _signal.signal(_enum_to_int(signalnum), _enum_to_int(handler))
  File "/home/milian/.local/lib/python3.9/site-packages/ipykernel/kernelbase.py", line 280, in pre_handler_hook
    self.saved_sigint_handler = signal(SIGINT, default_int_handler)
  File "/home/milian/.local/lib/python3.9/site-packages/ipykernel/kernelbase.py", line 257, in dispatch_shell
    self.pre_handler_hook()

the kernelbase.py code seems to reset the signal handler unconditionally to some default which is highly unexpected to me:

    def pre_handler_hook(self):
        """Hook to execute before calling message handler"""
        # ensure default_int_handler during handler call
        self.saved_sigint_handler = signal(SIGINT, default_int_handler)

Is there a way to prevent this from happening?

主要语言
Python
星标
734
派生
411
平均合并
1 天 2 小时
30 天内合并 PR
9

贡献指南

打开贡献指南

从这里开始

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

ipython/ipykernel 的其他 Issue

查看 ipython/ipykernel 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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