GNU bug report logs - #53136
28.0.90; segfault in lock_file

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Po Lu <luangruo <at> yahoo.com>
Cc: 53136 <at> debbugs.gnu.org
Subject: bug#53136: 28.0.90; segfault in lock_file
Date: Sun, 09 Jan 2022 09:36:36 +0200

> Resent-From: Po Lu <luangruo <at> yahoo.com>
> Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
> Resent-CC: bug-gnu-emacs <at> gnu.org
> Resent-Sender: help-debbugs <at> gnu.org
> Date: Sun, 09 Jan 2022 14:04:23 +0800
> From:  Po Lu via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs <at> gnu.org>
> 
> This write in `lock_file':
> 
>       memcpy (dot, replacement, replacementlen);
> 
> Ends up writing one byte outside dot.
> 
> I could not find the problem, but someone else may want to take a look.

Details, please: the values of all the relevant variables at that
point, including the contents of all the string variables.  And what
is your value of MAX_LFINFO?  I don't see how this can be efficiently
investigated without this data.  In particular, 'dot' has no storage
of its own, it's just a pointer into the lock_info.user[] array.

Previous Next

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