[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:30:00 +0200 |
> From: Po Lu <luangruo@yahoo.com>
> Cc: 53136@debbugs.gnu.org
> Date: Sun, 09 Jan 2022 21:23:14 +0800
>
> Po Lu <luangruo@yahoo.com> writes:
>
> > Thanks, I'll look into it.
>
> Perhaps the problem is in valgrind: when running under Valgrind, trying
> to lock that file makes lock_if_free return -2147459069.
>
> That shouldn't happen, right?
It's a strange value, no matter what.
- bug#53136: 28.0.90; segfault in lock_file, (continued)
- 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, 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, 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, Andreas Schwab, 2022/01/09
- bug#53136: 28.0.90; segfault in lock_file, Po Lu, 2022/01/09