Re: [gpsd-dev] Please test with WRITE_PAD zeroed

[Hal Murray]

[100 % CPU on a test that's hung.]
> The timeout happens when gpsd gets stuck waiting on a select because it
> never sees the injected "# EOF\n" at the end of the testload.  Python eating
> the  CPU is what's happening at the *other* end of the pipe. 

Why is the other end using the CPU when it's waiting for a response or the 
file to close?  I'd expect it to be waiting in a read.


-- 
These are my opinions.  I hate spam.