From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: MPS: Win64 testers? Date: Fri, 09 Aug 2024 09:00:11 +0300 Message-ID: <86y156kzh0.fsf@gnu.org> References: <86h6bxq3p3.fsf@gnu.org> <86sevho61y.fsf@gnu.org> <86ed70o90k.fsf@gnu.org> <86le17murx.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="24505"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org, pipcet@protonmail.com To: Quang Kien Nguyen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Aug 09 08:01:38 2024 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1scIh0-0006DM-17 for ged-emacs-devel@m.gmane-mx.org; Fri, 09 Aug 2024 08:01:38 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1scIgQ-0004E9-Bi; Fri, 09 Aug 2024 02:01:02 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1scIg9-0004C0-PT for emacs-devel@gnu.org; Fri, 09 Aug 2024 02:00:46 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1scIg8-0000sM-0s; Fri, 09 Aug 2024 02:00:44 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=5hiLfpUhiZ6sTd1EC6dAu+TeCo4vyiXH/nc+NnO5cXE=; b=J77CqjLESctN 8reIFIwmkkocXHrADNftiijLXj028UYQVyRrKRpPZAqZamA2VImnSsTu9oELmHumVduUvJTfNRYrs 1/Z9uDw+QH11N2G1nyh2K3n3okGJ0auG17kSHDASVLXawH+gNxqTPmG19wexDjVv872IvpkJd0ts0 okOMzXo1ejMcDw95MgaAG51vZJ4TrL90QZTl41vAoC0TPn5EX6x+0N+YgkQAXKE0HEbb+eDXCwHXI sjjFqEqlYKuXzJaWIMRJog3pZItqrm8uqHjtFhKNWsajmOhYJJN/LHJpY1DW3/gORmnR2sHcQjNe4 Glvi4mvlWj3Xnn/Twgmx2Q==; In-Reply-To: (message from Quang Kien Nguyen on Thu, 8 Aug 2024 16:44:09 -0700) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:322546 Archived-At: > From: Quang Kien Nguyen > Date: Thu, 8 Aug 2024 16:44:09 -0700 > Cc: emacs-devel@gnu.org, pipcet@protonmail.com > > > What ProcExp64 shows is a good sign, but I'd prefer to test also some > > redirection like above, with Emacs and the sub-process both writing to > > the same stdout/stderr stream, which would allow to verify positively > > that they write to different places. > > Okay, I have tested with this lisp exp: > (print 10 #'external-debugging-output) > > 10 is printed in the stdout/stderr on the console. > > Then try again with > (start-process-shell-command "test" nil "emacs -Q --batch --eval > \"(print 123123 #'external-debugging-output)\"") > > The child emacs process is spinned up but nothing is spewed to the > current console > output. Does that correct and prove that they don't share the handle? Not clearly enough. Consoles are tricky on Windows. It is better to start Emacs with stderr redirected to a file (I've shown how to do that in a previous message), and then see that what the child Emacs writes to external-debugging-output does not appear in that file. Also, instead of start-process please use call-process. That's because start-process redirects the stdout/stderr handles of the child process to the pipe from which the parent Emacs process reads, and that makes the experiment more complex and harder to reason about.