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 15:10:38 +0200

> From: Po Lu <luangruo <at> yahoo.com>
> Cc: 53136 <at> debbugs.gnu.org
> Date: Sun, 09 Jan 2022 21:00:53 +0800
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> > What is the contents of lock_info.user upto the first null byte?
> 
> It's "oldosfan" (which is correct).

No, it's not: it should be of the form USER <at> HOST.PID[:BOOT-TIME].  See
the commentary around line 288 in filelock.c.  The string is generated
in lock_file_1.  maybe you can step into it and see what happens
there.

What is "oldosfan"? is it the user or the host name?

Previous Next

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