[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: callback api, isearch, signals issue
From: |
Chet Ramey |
Subject: |
Re: callback api, isearch, signals issue |
Date: |
Sun, 8 Jan 2023 16:08:52 -0500 |
User-agent: |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.6.1 |
On 1/6/23 10:07 AM, Andrew Burgess wrote:
Hi,
While working on GDB, which uses the callback API, I've run into some
issues relating to reverse isearch and signal handling.
At the end of this email is a small example program that uses the
callback API. This is a modified version of the example program that
is included in the readline manual.
The issue I have relies on a SIGINT arriving at just the wrong time.
To reproduce this the test program uses rl_getc_function to setup a
wrapper function (my_getc) that calls rl_getc. After a couple of
times calling my_getc, a SIGINT is sent to the process using kill().
Two questions: what does gdb do when it gets the SIGINT? Readline sends it
back to the calling application. I assume it just sets a flag? And does
gdb set rl_signal_event_hook?
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
- callback api, isearch, signals issue, Andrew Burgess, 2023/01/06
- Re: callback api, isearch, signals issue,
Chet Ramey <=
- Re: callback api, isearch, signals issue, Andrew Burgess, 2023/01/09
- Re: callback api, isearch, signals issue, Chet Ramey, 2023/01/09
- Re: callback api, isearch, signals issue, Andrew Burgess, 2023/01/11
- Re: callback api, isearch, signals issue, Chet Ramey, 2023/01/11
- Re: callback api, isearch, signals issue, Andrew Burgess, 2023/01/11