[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
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)?

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