From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: 53136@debbugs.gnu.org
Subject: bug#53136: 28.0.90; segfault in lock_file
Date: Sun, 09 Jan 2022 14:56:54 +0200 [thread overview]
Message-ID: <83wnj99ieh.fsf@gnu.org> (raw)
In-Reply-To: <875yqtt9qk.fsf@yahoo.com> (message from Po Lu on Sun, 09 Jan 2022 19:43:47 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: 53136@debbugs.gnu.org
> Date: Sun, 09 Jan 2022 19:43:47 +0800
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > So we somehow wrote more than 8192 bytes by that memcpy line? I find
> > this hard to believe.
>
> Manual inspection of the core dump seems to reveal something very
> different from what the debugger said (and I asked for a second opinion
> on this as well):
>
> - lock_info.dot and lock_info.colon are NULL.
> - lock_filename is a Lisp string, the data is
> "/home/oldosfan/Mail/archive/sent/2022-01".
> - handler, subject_buf are NULL
> - dot is NULL
> - pidlen is -1 (long int)
> - replacementlen is 6
On second thought, these values are strange. Is PC really at the
memcpy line? I don't see how dot could be NULL at that point: if
lock_if_free returns a negative value, lock_info.dot cannot be NULL,
according to my reading of the code.
What is the contents of lock_info.user upto the first null byte?
next prev parent reply other threads:[~2022-01-09 12:56 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
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 [this message]
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=83wnj99ieh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=53136@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).