Hi, leave them on!
It's always better to have the log immediately available, then to repeat all the steps to the problem. Extra important if the "setup phase" of your debug session is long and cumbersome (At least Marc knows what I mean ;).... I think that the availability of the info is important (and indeed user friendly) and that it doesn't matter if internals of CDT are exposed since it's open source anyway.
/Jonas
-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Marc Khouzam
Sent: den 30 april 2012 16:08
To: 'xgsa'; 'CDT General developers list.'
Subject: Re: [cdt-dev] Why the gdb traces are enabled by default?
> -----Original Message-----
> From: xgsa [mailto:xgsa@xxxxxxxxx]
> Sent: Saturday, April 28, 2012 2:37 PM
> To: CDT General developers list.
> Cc: Marc Khouzam
> Subject: Re: [cdt-dev] Why the gdb traces are enabled by default?
>
> I think that gdb traces have no value for the CDT user (I mean not a
> developer and not a user analyzing the problem in CDT/gdb). However,
> they are shown in consoles list and reveal the CDT internals.
> Could you
> please take an example when the traces could be useful (except of the
> enumerated cases which seems not very often in CDT release)?
Originally, I enabled the 'gdb traces' by default because DSF-GDB was becoming the new default debugger for CDT, and I wanted to make it easier for us to deal with potential issues quickly.
Now that things have gone pretty well, it may not be as important.
Does anyone else feel it would be more user-friendly to hide those traces by default?
>
> Anton
>
> -------- Original message --------
> > Since the traces are in their own console, they don't
> bother the user. Having them on by default brings more value.
> >
> > Why do you prefer them off?
> >
> >
> > Best regards,
> >
> > Marc
> >
> >
> > ----- Original Message -----
> > From: xgsa<xgsa@xxxxxxxxx>
> > To: "CDT General developers list."<cdt-dev@xxxxxxxxxxx>
> > Sent: 27-04-2012 15:14
> > Subject: [cdt-dev] Why the gdb traces are enabled by default?
> >
> >
> >
> > Hi,
> >
> > I am wondering why the "C/C++ --> Debug --> GDB -->
> Enable GDB traces"
> > preference is enabled by default? Certainly, it is very helpful for
> > developers and could be used by advanced users trying to analyze the
> > debug problem. However, it seems useless for the most users
> which just
> > use CDT, so I propose to disable it by default.
> >
> > If there are no objections I could provide a patch.
> >
> >
> > Thanks,
> > Anton.
> > _______________________________________________
> > cdt-dev mailing list
> > cdt-dev@xxxxxxxxxxx
> >
https://dev.eclipse.org/mailman/listinfo/cdt-dev
> > _______________________________________________
> > cdt-dev mailing list
> > cdt-dev@xxxxxxxxxxx
> >
https://dev.eclipse.org/mailman/listinfo/cdt-dev
> >
> >
>
>
>
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
