[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#53136: 28.0.90; segfault in lock_file
From: |
Eli Zaretskii |
Subject: |
bug#53136: 28.0.90; segfault in lock_file |
Date: |
Sun, 09 Jan 2022 15:10:38 +0200 |
> From: Po Lu <luangruo@yahoo.com>
> Cc: 53136@debbugs.gnu.org
> Date: Sun, 09 Jan 2022 21:00:53 +0800
>
> Eli Zaretskii <eliz@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@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?
- bug#53136: 28.0.90; segfault in lock_file, (continued)
- bug#53136: 28.0.90; segfault in lock_file, Eli Zaretskii, 2022/01/11
- bug#53136: 28.0.90; segfault in lock_file, Po Lu, 2022/01/11
- bug#53136: 28.0.90; segfault in lock_file, Paul Eggert, 2022/01/11
- bug#53136: 28.0.90; segfault in lock_file, Po Lu, 2022/01/11
- bug#53136: 28.0.90; segfault in lock_file, Po Lu, 2022/01/10
- bug#53136: 28.0.90; segfault in lock_file, Eli Zaretskii, 2022/01/11
- bug#53136: 28.0.90; segfault in lock_file, Eli Zaretskii, 2022/01/09
- bug#53136: 28.0.90; segfault in lock_file, Po Lu, 2022/01/09
- bug#53136: 28.0.90; segfault in lock_file,
Eli Zaretskii <=
- bug#53136: 28.0.90; segfault in lock_file, Po Lu, 2022/01/09
- bug#53136: 28.0.90; segfault in lock_file, Po Lu, 2022/01/09
- bug#53136: 28.0.90; segfault in lock_file, Eli Zaretskii, 2022/01/09
- bug#53136: 28.0.90; segfault in lock_file, Andreas Schwab, 2022/01/09
- bug#53136: 28.0.90; segfault in lock_file, Po Lu, 2022/01/09