From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Eli Zaretskii <eliz@gnu.org>, 53136@debbugs.gnu.org
Subject: bug#53136: 28.0.90; segfault in lock_file
Date: Tue, 11 Jan 2022 08:51:25 +0800 [thread overview]
Message-ID: <8735lvp01e.fsf@yahoo.com> (raw)
In-Reply-To: <37cd3017-38cb-fa2c-7b52-fbeb3b085744@cs.ucla.edu> (Paul Eggert's message of "Mon, 10 Jan 2022 15:11:04 -0800")
Paul Eggert <eggert@cs.ucla.edu> writes:
> On 1/9/22 04:03, Eli Zaretskii wrote:
>
>> Paul, could you please take a look?
>
> The problem (as Po deduced) seems to be that Haiku errno values are
> negative by default.
That was an unrelated problem. This bug is on GNU/Linux, when running
under Valgrind. (I was trying to find the GC bug from last month.)
> 1. It uses BE_USE_POSITIVE_POSIX_ERRORS but Haiku spells it
> B_USE_POSITIVE_POSIX_ERRORS.
I'll fix that.
> 2. There's no need to replace "if (err < 0)" with "if (err == -1 ||
> err == -2)", as this replacement is not needed given the "#if !defined
> HAIKU ..." stuff.
> 3. More importantly, I'm sure there are other places where Emacs
> assumes that errno values are positive. I doubt whether it's
> reasonable to expect Emacs developers to remember and work around this
> Haiku incompatibility, every time they call a function that sets errno
> or returns an errno value. Instead, we should arrange for Haiku builds
> to use positive errno values, they way errno behaves on GNU and other
> POSIX-compatible hosts. This should be a much more maintainable
> solution.
I would prefer for us to find and fix those instances manually, because
B_USE_POSITIVE_POSIX_ERRORS is some kind of stopgap measure for porting
POSIX utilities like sshfs, and prevents some other functionality from
working correctly (i.e. apparently it's an error to -ltracker with it
defined, so file dialogs won't work.)
Thanks.
next prev parent reply other threads:[~2022-01-11 0:51 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <871r1hv40o.fsf.ref@yahoo.com>
2022-01-09 6:04 ` bug#53136: 28.0.90; segfault in lock_file Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-09 7:36 ` Eli Zaretskii
2022-01-09 8:10 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-09 8:42 ` Eli Zaretskii
2022-01-09 9:40 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-09 11:43 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-09 12:03 ` Eli Zaretskii
2022-01-10 23:11 ` Paul Eggert
2022-01-10 23:30 ` Paul Eggert
2022-01-11 0:51 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-11 0:51 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-01-11 1:05 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-12 2:59 ` Paul Eggert
2022-01-12 3:04 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-12 19:22 ` Paul Eggert
2022-01-11 12:45 ` Eli Zaretskii
2022-01-11 13:16 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-11 17:05 ` Paul Eggert
2022-01-12 0:35 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-11 0:58 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-11 12:30 ` Eli Zaretskii
2022-01-09 12:56 ` Eli Zaretskii
2022-01-09 13:00 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-09 13:10 ` Eli Zaretskii
2022-01-09 13:16 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-09 13:23 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-09 13:30 ` Eli Zaretskii
2022-01-09 13:47 ` Andreas Schwab
2022-01-10 0:29 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=8735lvp01e.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=53136@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=eliz@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).