Re: Single process output reading

[Milan Zamazal]

>>>>> "KFS" == Kim F Storm <address@hidden> writes:

    KFS> blocking everything including timers isn't very good, but may
    KFS> be acceptable for very short periods of time.

Yes, that's what I need.

    KFS> Here's an (untested) patch that adds a "just-this-one" arg to
    KFS> accept-process-output

Thanks!

Unfortunately, when called as follows:

  (accept-process-output your-process nil nil 1)

Emacs segfaults.  FWIW, the traceback is 

  #0  0x08186fa7 in wait_reading_process_input (time_limit=-1, microsecs=0,
      read_kbd=0, do_display=0) at process.c:4275
  #1  0x08186574 in Faccept_process_output (process=148636188, timeout=0,
      timeout_msecs=138317841, just_this_one=8) at process.c:3781
  #2  0x08154eb8 in Feval (form=138037816) at eval.c:2101
  ...

The problem is that wait_channel is -1 on the segfaulting line:

  FD_SET (wait_channel, &Available);

I don't understand it, since wait_proc->infd is 72 (`pr' says 9) and the
same call without the JUST-THIS-ONE argument

  (accept-process-output your-process nil nil nil)

works fine.

Regards,

Milan Zamazal

-- 
It is the reformer, who is anxious for the reform, and not society, from which
he should expect nothing better than opposition, abhorrence and even mortal
persecution.                                                   -- M. K. Gandhi