Re: bash 4.0p17 problem with CTRL+C

[Chet Ramey]

Alan Hourihane wrote:
> On Fri, 2009-05-15 at 13:19 +0200, Roman Rakus wrote:
>> On 05/15/2009 12:02 PM, Alan Hourihane wrote:
>>> Hi all,
>>>
>>> I've just compiled bash 4.0 p17 and noticed that CTRL+C isn't having any
>>> effect until I hit<return>.
>>>
>>> bash 3.2 worked perfectly, so I'm a little unsure what's caused this.
>>>
>>> Can anyone point me at the code which handles this and I can take a
>>> closer look ?
>>>
>>> Thanks,
>>>
>>> Alan.
>>>
>>>
>>>
>>>    
>> Probably in readline. If it occurs on command prompt. If in running 
>> script it's in bash.
> 
> It's on the command line. Which function handles that in bash ?

You can debug an interactive bash and put a breakpoint in
rl_signal_handler.  This should give you information about whether
bash is receiving the SIGINT and what it's doing with it.

Chet
-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer

Chet Ramey, ITS, CWRU    chet@case.edu    http://cnswww.cns.cwru.edu/~chet/