unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: 71477@debbugs.gnu.org
Subject: bug#71477: 30.0.50; Lock files are not deleted on Windows 98
Date: Tue, 11 Jun 2024 16:03:01 +0300	[thread overview]
Message-ID: <861q537htm.fsf@gnu.org> (raw)
In-Reply-To: <87jzivamzp.fsf@yahoo.com> (message from Po Lu on Tue, 11 Jun 2024 16:43:06 +0800)

> From: Po Lu <luangruo@yahoo.com>
> Cc: 71477@debbugs.gnu.org
> Date: Tue, 11 Jun 2024 16:43:06 +0800
> 
> > The only possible issue I see with allowing a negative PID is that the
> > code checks for "pid > 0" or "pid < 0" somewhere; if that is the case,
> > we should replace those with comparisons with -1 instead.
> >
> > Can you test the above on Windows 9X when you have a chance?  Then we
> > could install it.
> 
> If it doesn't produce any adverse effect on modern Windows, and what I
> raised is not important, let's install it now, and I will test it as
> soon as may be, or it might fall by the wayside.

OK, but could you provide some additional details, so I could
understand the issue better?  What kind of negative values do you get
from getpid on Windows 98, and what does the system show as the PID of
that process?  Is the value really such a large positive number that
its MSB is set?

According to my records, _getpid just calls GetCurrentProcessId and
returns the value as an int.  So for _getpid to return a negative
value, GetCurrentProcessId should return a very large positive value,
I think.





  parent reply	other threads:[~2024-06-11 13:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87r0d4bzut.fsf.ref@yahoo.com>
2024-06-10 15:07 ` bug#71477: 30.0.50; Lock files are not deleted on Windows 98 Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-10 17:44   ` Eli Zaretskii
     [not found]     ` <87ikygb6hp.fsf@yahoo.com>
2024-06-11  6:47       ` Eli Zaretskii
     [not found]         ` <87bk47c4cd.fsf@yahoo.com>
2024-06-11  7:56           ` Eli Zaretskii
     [not found]             ` <871q53c2ur.fsf@yahoo.com>
2024-06-11  8:28               ` Eli Zaretskii
     [not found]                 ` <87jzivamzp.fsf@yahoo.com>
2024-06-11 13:03                   ` Eli Zaretskii [this message]
2024-06-11 13:34                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-06-12  8:25                   ` Eli Zaretskii
2024-06-12 16:07                     ` Paul Eggert
2024-06-12 17:10                       ` Eli Zaretskii
2024-06-12 17:57                         ` Paul Eggert
2024-06-13  8:06                           ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=861q537htm.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=71477@debbugs.gnu.org \
    --cc=luangruo@yahoo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).