Re: Reintroducing critical warnings?

[Bastien Nocera <hadess hadess net>]

On Tue, 2008-02-19 at 22:05 -0500, Havoc Pennington wrote:
> Hi,
> 
> On Feb 19, 2008 6:31 PM, Bastien Nocera <hadess hadess net> wrote:
> >
> > On Wed, 2008-02-20 at 00:25 +0100, Vincent Untz wrote:
> > > Le mardi 19 février 2008, à 23:46 +0100, Wouter Bolsterlee a écrit :
> > > > 2008-02-19 klockan 21:20 skrev Christian Neumair:
> > > > > I hereby propose to reintroduce the critical warnings we used to have
> > > > > during unstable release cycles.
> > > >
> > > > Unstable gnome-session builds (eg. minor version is odd) set the G_DEBUG
> > > > variable by default, so this should still work.
> > >
> > > Most distros have a patch to remove this "feature", though :/
> >
> > The problem is that it crashes the app when it prints a simple and
> > usually harmless warning. It should just dump a backtrace instead, and
> > the execution of the program carry on.
<snip>
> But I guess the ability to invoke bug-buddy without crashing might be
> a nice approach.

That was pretty much my badly made point, you just assumed "printing"
was printing on the stdout/stderr ;)