GNU bug report logs - #3399
Crash in multi-TTY mode

Previous Next

Package: emacs;

Reported by: "Shannon Jones" <cz2s20d02 <at> sneakemail.com>

Date: Wed, 27 May 2009 02:50:03 UTC

Severity: normal

Merged with 3407

Done: Chong Yidong <cyd <at> stupidchicken.com>

Bug is archived. No further changes may be made.

Full log

View this message in rfc822 format

From: Stefan Monnier <monnier <at> iro.umontreal.ca>
To: YAMAMOTO Mitsuharu <mituharu <at> math.s.chiba-u.ac.jp>
Cc: 3399 <at> debbugs.gnu.org, Shannon Jones <cz2s20d02 <at> sneakemail.com>
Subject: bug#3399: Crash in multi-TTY mode
Date: Thu, 28 May 2009 09:14:06 -0400

>   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
This bug report was last modified 15 years and 183 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.