[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Abysmal state of GTK build
From: |
Po Lu |
Subject: |
Re: Abysmal state of GTK build |
Date: |
Sun, 21 Aug 2022 22:04:13 +0800 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.91 (gnu/linux) |
Lars Ingebrigtsen <larsi@gnus.org> writes:
> As I've said, the crash should be fixed on our side. You claim that
> that's impossible, but I'm sure a work-around can be done (because
> anything is possible).
It is really not fixable. The NULL dereference is caused by GTK
mishandling an event, and we cannot withhold the event from GTK, because
then the next motion event from a newly hotplugged device will be enough
to make it crash with the same NULL dereference.
- Re: Abysmal state of GTK build, (continued)
- Re: Abysmal state of GTK build, Po Lu, 2022/08/24
- Re: Abysmal state of GTK build, Lars Ingebrigtsen, 2022/08/24
- Re: Abysmal state of GTK build, Po Lu, 2022/08/24
- Re: Abysmal state of GTK build, Lars Ingebrigtsen, 2022/08/24
- Re: Abysmal state of GTK build, Po Lu, 2022/08/24
- Changing the make setup for Emacs, Richard Stallman, 2022/08/24
- change the Subject line (was: Changing the make setup for Emacs), andrés ramírez, 2022/08/26
- Re: Abysmal state of GTK build, Lars Ingebrigtsen, 2022/08/21
- Re: Abysmal state of GTK build, Po Lu, 2022/08/21
- Re: Abysmal state of GTK build, Lars Ingebrigtsen, 2022/08/21
- Re: Abysmal state of GTK build,
Po Lu <=
- Re: Abysmal state of GTK build, Lars Ingebrigtsen, 2022/08/21
- Re: Abysmal state of GTK build, Po Lu, 2022/08/21
- Re: Abysmal state of GTK build, Gregory Heytings, 2022/08/21
- Re: Abysmal state of GTK build, Po Lu, 2022/08/21
- Re: Abysmal state of GTK build, Lars Ingebrigtsen, 2022/08/22
- Re: Abysmal state of GTK build, Po Lu, 2022/08/22
- Re: Abysmal state of GTK build, Lars Ingebrigtsen, 2022/08/22
- Re: Abysmal state of GTK build, Po Lu, 2022/08/22
- Re: Abysmal state of GTK build, Lars Ingebrigtsen, 2022/08/22
- Re: Abysmal state of GTK build, Po Lu, 2022/08/22