On Tue, May 14, 2013 at 05:39:17AM +0100, Andy Koppe wrote:
>On 14 May 2013 01:23, Jack Adrian Zappa wrote:
>>In any case, how does Linux deal with this issue?
>
>I don't know. A buffer on the terminal's side of the pty? Automatic
>deadlock detection in the kernel, causing one of the blocking wri
On 14 May 2013 01:23, Jack Adrian Zappa wrote:
> On Mon, May 13, 2013 at 5:45 PM, Andy Koppe wrote:
>>
>> On 13 May 2013 22:35, Adrian H wrote:
>> > I inadvertently dumped a binary stream to the terminal and it froze
>> > mintty. When I tried to kill the process dumping the data, it
>> > wouldn't
On Mon, May 13, 2013 at 10:45:17PM +0100, Andy Koppe wrote:
>On 13 May 2013 22:35, Adrian H wrote:
>> I inadvertently dumped a binary stream to the terminal and it froze
>> mintty. When I tried to kill the process dumping the data, it
>> wouldn't die, even when using -9 switch. When I used Proces
On Mon, May 13, 2013 at 5:45 PM, Andy Koppe wrote:
>
> On 13 May 2013 22:35, Adrian H wrote:
> > I inadvertently dumped a binary stream to the terminal and it froze
> > mintty. When I tried to kill the process dumping the data, it
> > wouldn't die, even when using -9 switch. When I used Process
On 13 May 2013 22:35, Adrian H wrote:
> I inadvertently dumped a binary stream to the terminal and it froze
> mintty. When I tried to kill the process dumping the data, it
> wouldn't die, even when using -9 switch. When I used Process Explorer
> to kill it, it died and mintty resumed working.
>
>
I inadvertently dumped a binary stream to the terminal and it froze
mintty. When I tried to kill the process dumping the data, it
wouldn't die, even when using -9 switch. When I used Process Explorer
to kill it, it died and mintty resumed working.
I narrowed the stream down to 370 'lines' by cat
6 matches
Mail list logo
