[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MiNT] bash ^C bug

To: mint@lists.fishpool.fi
Subject: Re: [MiNT] bash ^C bug
From: Vincent Rivière <vincent.riviere@freesbee.fr>
Date: Wed, 11 Apr 2012 23:48:37 +0200
In-reply-to: <4F85DD83.4090207@fairlite.co.uk>
List-help: <mailto:ecartis@lists.fishpool.fi?Subject=help>
List-id: <mint.lists.fishpool.fi>
List-owner: <mailto:tjhukkan@fishpool.fi>
List-post: <mailto:mint@lists.fishpool.fi>
List-subscribe: <mailto:mint-request@lists.fishpool.fi?Subject=subscribe>
List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
References: <4F27B3EC.40902@fairlite.co.uk> <4F27BF11.1080403@freesbee.fr> <4F27C4F7.3050707@fairlite.co.uk> <4F27CDE9.9040208@freesbee.fr> <4F27FABC.8050105@fairlite.co.uk> <4F2802FB.7060905@freesbee.fr> <4F285493.2030702@freesbee.fr> <4F29310E.7070807@fairlite.co.uk> <4F85DD83.4090207@fairlite.co.uk>
Sender: mint-bounce@lists.fishpool.fi
User-agent: Mozilla/5.0 (Windows NT 5.1; rv:11.0) Gecko/20120327 Thunderbird/11.0.1

Alan Hourihane wrote:

Turns out it was a kernel bug. Committed a fix just a few moments ago.


Amazing! It works fine 8-)
Now ^C does the right thing in bash, without recompiling it.

I saw you made changes about the "interrupted system call" stuff.
So the bug was not related to SA_RESTART?

--
Vincent Rivière

Follow-Ups:
- Re: [MiNT] bash ^C bug
  - From: Alan Hourihane <alanh@fairlite.co.uk>

References:
- Re: [MiNT] bash ^C bug
  - From: Alan Hourihane <alanh@fairlite.co.uk>

Prev by Date: Re: [MiNT] bash ^C bug
Next by Date: Re: [MiNT] bash ^C bug
Previous by thread: Re: [MiNT] bash ^C bug
Next by thread: Re: [MiNT] bash ^C bug
Index(es):
- Date
- Thread