GNU bug report logs - #33050
27.0.50; [macOS] Problem with process input with process-connection-type nil

Previous Next

Full log

Message #23 received at 33050 <at> debbugs.gnu.org (full text, mbox):

From: Filipp Gunbin <fgunbin <at> fastmail.fm>
To: Thomas Fitzsimmons <fitzsim <at> fitzsim.org>
Cc: Eli Zaretskii <eliz <at> gnu.org>, 33050 <at> debbugs.gnu.org
Subject: Re: bug#33050: 27.0.50;
 [macOS] Problem with process input with process-connection-type nil
Date: Wed, 24 Oct 2018 16:13:26 +0300

Thomas,

On 23/10/2018 21:55 -0400, Thomas Fitzsimmons wrote:

>>> Your test case behaves the same way for me on x86_64 GNU/Linux.
>>
>> Do you mean it fails, or it works ok (regardless of
>> process-connection-type value)?
>
> I meant its behaviour is the same for me on x86_64 GNU/Linux as what you
> described its behaviour to be on Mac OS.  Without:
>
> (process-connection-type nil)
>
> the test case succeeds.  With it, the test case hangs.

Good that it can be "reproduced" at least in this form.

If I change args to "ldapsearch" "-W" (and prompt, accordingly), then

- with process-connection-type t, the test exits normally, and buffer
  contains the same text as for you:

  Enter LDAP Password: 
  ldap_sasl_interactive_bind_s: Can't contact LDAP server (-1)

  Process my-process exited abnormally with code 255

- with process-connection-type nil, the test hangs, and when I quit, the
  buffer contains:

  Process my-process stopped (tty output): 22

I see that /usr/bin/read is not the best thing to test with, because I
don't know exactly what it's doing.

My ldapsearch (2.4.28) is from macOS - they don't update it frequently.

I'll try a later version.  Other than that, I don't know what to do for
now :-(

Filipp

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.