This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH 2/4]: Handle SIGINT under Python by raising KeyboardInterrupt


>>>>> "Yit" == Khoo Yit Phang <khooyp@cs.umd.edu> writes:

Yit> This assumes that GDB's SIGINT handler only sets quit_flag, and that
Yit> GDB never changes the SIGINT handler and overrides the Python SIGINT
Yit> handler? I vaguely recall encountering the latter issue which led me
Yit> to the current implementation. A grep of GDB shows four places that
Yit> call "signal (SIGINT, handle_sigint)" in event-top.c, record.c, and
Yit> remote.c.

At first I was pretty confident in my approach, but I searched a bit
again, and found even more places that install SIGINT handlers, and so
now I am not so sure.

I think adding macros that use your new functions is probably the best
way to go.

Tom


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]