Re: Can't stop find-grep-dired when using Cygwin for the inferior process

[Kim F. Storm]

Lennart Borgman <address@hidden> writes:

> Kim F. Storm wrote:
>>> The problem on w32 is that w32 sends a message to the process when
>>> delete-process is used. W32 then expects the process to answer to some
>>> w32 message (can't remember which one right now). Cygwin does not
>>> answer to this message. Then w32 shows a dialog box and asks the user
>>> what to do.
>>>     
>>
>>
>> AFAICS, delete-process invokes kill-process to kill the process; the
>> rest of delete-process is just book-keeping.
>>
>> IIUC you say kill-process works (or is it only interrupt_process which
>> works?) instead of delete-process ?
>>
>> But kill-process on cygwin should just invoke "cygwin kernel's kill"
>> so why does the cygwin code use the w32 message interface?
>>
>> -- or am I missing something.
>>   
> At the moment I am very confused about what actually happened. I was
> testing another software firewall, but since things went very slow
> with I switched back to my old software firewall.

How can the choice of firewall influence whether delete-process
works or not?

> After that I tested again and I was going to say that the problem is
> gone. It is nearly - but not quite. Most of the times kill-find works
> now, but once Emacs froze like before. Could this be some kind of race
> condition?

Without knowing what emacs was doing or waiting for, nobody can tell!

> It could be problems with my PC. There is something wrong I think, but
> I have not been able to find out what.

Your PC has installed a certain non-free o/s, right?
That's problem number one!  :-)
So indeed, you should start by fixing your PC.  :-)


> At the moment I do not know what to test and I do not understand how
> to read the C code. How do I know the values of the different
> constants used by ifdef? I began writing something that would let me
> know that, but I did not quite finish it.

If you are just interested in a few defines, just printf them in main.

>
>> AFAICS, delete-process calls kill-process, so it looks like a loop
>> in some of the book-keeping in delete-process ... can you find that
>> loop?  IOW, what is emacs doing when it "hangs" ?
>>   
> It does not look like a loop. Emacs eats no CPU.

It is probably waiting for some event then.  A backtrace
should show you where it is waiting, and the state may
then show you what it is waiting for.

-- 
Kim F. Storm <address@hidden> http://www.cua.dk