[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#53136: 28.0.90; segfault in lock_file
From: |
Po Lu |
Subject: |
bug#53136: 28.0.90; segfault in lock_file |
Date: |
Tue, 11 Jan 2022 13:16:35 +0000 (UTC) |
[Sorry for the webmail, but Yahoo SMTP is wedged; I hope Reply All
worked and this reaches the bug tracker]
> Ugh!
I agree completely.
> Fixing each place individually is a time bomb: no one will remember
> that after enough time has passed, and we will add bugs.
> The only alternative is to filter errno via some macro, which will do
> nothing on all platforms but Haiku, where it will map them to Posix
> values. Butt-ugly, but it's not our fault.
Hmm, perhaps gnulib can do something in this area? Paul, any ideas?
Thanks in advance.
- 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, Po Lu, 2022/01/10
- 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, Paul Eggert, 2022/01/12
- 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 <=
- 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, 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, 2022/01/09