[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#3399: Crash in multi-TTY mode
From: |
Stefan Monnier |
Subject: |
bug#3399: Crash in multi-TTY mode |
Date: |
Thu, 28 May 2009 09:14:06 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/23.0.94 (gnu/linux) |
> 1. Older libX11 that doesn't care about XlibDisplayDfltRMDB at all.
> 2. Newer libX11, when the first XGetDefault call sets dpy->db to a
> non-NULL value.
> 3. Newer libX11, when the first XGetDefault call sets dpy->db to NULL.
> Case 3 corresponds to the problematic scenario I mentioned in my
> previous mail and the other cases should work fine currently. Undoing
> my recent change means that we don't destroy the database ourselves,
> and it leaks memory in Case 2 and 3.
What if (as asked) we don't just undo your change, but additionally
return to freeing the DB (so we'll get a crash in case 1)? Will we then
also get a crash in case 2 or 3?
Stefan
- bug#3399: Crash in multi-TTY mode, Shannon Jones, 2009/05/27
- bug#3399: Crash in multi-TTY mode, YAMAMOTO Mitsuharu, 2009/05/27
- bug#3399: Crash in multi-TTY mode, Stefan Monnier, 2009/05/27
- bug#3399: Crash in multi-TTY mode, YAMAMOTO Mitsuharu, 2009/05/27
- bug#3399: Crash in multi-TTY mode, YAMAMOTO Mitsuharu, 2009/05/27
- bug#3399: Crash in multi-TTY mode,
Stefan Monnier <=
- bug#3399: Crash in multi-TTY mode, YAMAMOTO Mitsuharu, 2009/05/29
- bug#3399: Crash in multi-TTY mode, Stefan Monnier, 2009/05/29
- bug#3399: Crash in multi-TTY mode, YAMAMOTO Mitsuharu, 2009/05/29
- bug#3399: Crash in multi-TTY mode, Stefan Monnier, 2009/05/30
- bug#3399: Crash in multi-TTY mode, YAMAMOTO Mitsuharu, 2009/05/31