As I said in IRC, I'm not terribly convinced we do a great job of fixing the crashes we already have, much less all the new crashes this will introduce. But I'm willing to be swayed by analysis of the incoming/outgoing crasher bug flow we currently have.
Luis On 11/6/05, Vincent Untz <[EMAIL PROTECTED]> wrote: > Hey, > > The next releases of glib (HEAD and glib-2-8) will support a new debug > flag for the G_DEBUG environment variable: fatal_criticals. This make > the program crash on critical warnings. > > I propose to use this nice feature during the development cycles to help > eradicate all these critical warnings. I made a simple patch for > gnome-session: > http://www.gnome.org/~vuntz/tmp/gnome-session.diff > > Why? Well, we currently have critical warnings in a lot of modules. And > we don't care since we don't notice them. With this, we could easily > notice them and have nice stack traces to fix them. This should result > in less bugs. > > Does it make the desktop unusable? Well, the wncklet-applet crashes [1], > it seems bug-buddy crashes on Fedora [2] and, err, I can't use > evolution ;-) More crashes are expected, but I think the sooner we fix > the critical warnings, the better. > > What do you think? > > [1] http://bugzilla.gnome.org/show_bug.cgi?id=149326 with a patch > [2] http://bugzilla.gnome.org/show_bug.cgi?id=320062 > > Vincent > > -- > Les gens heureux ne sont pas pressés. > > _______________________________________________ > desktop-devel-list mailing list > [email protected] > http://mail.gnome.org/mailman/listinfo/desktop-devel-list > _______________________________________________ desktop-devel-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/desktop-devel-list
