[Top][All Lists]

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

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

From: Eric S. Raymond
Subject: Re: [gpsd-dev] Please test with WRITE_PAD zeroed
Date: Sun, 15 Feb 2015 20:45:10 -0500
User-agent: Mutt/1.5.23 (2014-03-12)

Hal Murray <address@hidden>:
> [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.

I have no idea. It's *difficult* to figure out what a scripting language
like Python is actually doing at the tty and socket layer - you get all kinds
of unexpected interactions between different layers of the stack.
                <a href="";>Eric S. Raymond</a>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]