| Re: [cdt-dev] Indexer polluting the log file |
Hi, I believe Jason is referring to the new General->Tracing preference page (see screenshot) which allows to turn on/off DebugTrace without restarting Eclipse. It also allows to enable/disable the logging to trace.log. Only DSF-GDB is making use of it in CDT at this time and only on the master branch but Jason has posted patches to have other CDT components use it. Using this, if the indexer printouts were off by default, they could be turned on more easily, or they could be enabled by default for a product. It does not sound like a perfect solution to the discussion but it is worth mentioning. Marc -- This Communication is Confidential. We only send and receive email on the basis of the terms set out at www.ericsson.com/email_disclaimer > -----Original Message----- > From: cdt-dev-bounces@xxxxxxxxxxx > [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Cortell John-RAT042 > Sent: Friday, August 24, 2012 10:59 AM > To: Jason Litton; CDT General developers list. > Subject: Re: [cdt-dev] Indexer polluting the log file > > Conditional tracing isn't new. Many plug-ins in CDT have been > making use of it for years (see attached screenshot). Not > trying to marginalize any improvements you may have made in > that area; just saying the concept and practice has been > around for quite some time. The current debate is not about > whether it's possible or even convenient to make the indexer > trace conditional; it's about whether it should be on by > default and if the .log file is the proper place for the output. > > John > > > -----Original Message----- > > From: cdt-dev-bounces@xxxxxxxxxxx > [mailto:cdt-dev-bounces@xxxxxxxxxxx] On > > Behalf Of Jason Litton > > Sent: Friday, August 24, 2012 9:24 AM > > To: CDT General developers list. > > Subject: Re: [cdt-dev] Indexer polluting the log file > > > > FWIW, it looks to me that this could be resolved by using > the Platform > > Debug Trace that I've submitted patches to use. That way, > in a shipping > > product, you could turn the trace on or off as you want. We > could decide > > whether it would default to off or on, but switching from > that default > > would be easy. > > > > ----- Original Message ----- > > From: "Doug Schaefer" <dschaefer@xxxxxxx> > > To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx> > > Sent: Friday, August 24, 2012 7:52:50 AM > > Subject: Re: [cdt-dev] Indexer polluting the log file > > > > > > > > We could log the exception every time there is a unresolved > symbol. Or we > > can summarize it into a single log entry as we are doing > now, maybe only > > logging it when there are unresolved symbols or other problems. > > > > > > From: Cortell John-RAT042 < RAT042@xxxxxxxxxxxxx > > > Reply-To: "CDT General developers list." < cdt-dev@xxxxxxxxxxx > > > Date: Friday, 24 August, 2012 9:18 AM > > To: "CDT General developers list." < cdt-dev@xxxxxxxxxxx > > > Subject: Re: [cdt-dev] Indexer polluting the log file > > > > > > > > > > > > I'm sorry, but I have to respond to this one. This all makes perfect > > sense, but the crux of the matter lies in your last sentence. > > > > > > "...option should be on per default in order to serve > people that report > > problems." > > > > > > Again, there is no shortage of problems that can occur in > Eclipse. This > > rationale does not scale well. The log file would be jam packed with > > trace information if other feature developers took the same > position. > > Perhaps, though, you would see that as acceptable. I suppose it's a > > matter of perspective on the role of the log file. What I > am certain of > > is that, by and large, Eclipse project plug-in developers take the > > perspective that it's for error reporting and not tracing, > certainly not > > tracing that's on by default. > > > > > > John > > > > > > > > > > > > > > > > From: cdt-dev-bounces@xxxxxxxxxxx [ cdt-dev-bounces@xxxxxxxxxxx ] on > > behalf of Schorn, Markus [ Markus.Schorn@xxxxxxxxxxxxx ] > > Sent: Friday, August 24, 2012 3:52 AM > > To: CDT General developers list. > > Subject: Re: [cdt-dev] Indexer polluting the log file > > > > > > > > > > > > > > Hi, > > > > The information in the log is helpful for two things: > > > > * It provides you feedback about the quality of the > indexing and you do > > not have another way of getting this kind of information. > > > > * When an index related issue (navigation, semantic > highlighting, ...) is > > reported you have a quick way of figuring out whether the > reporter has a > > reasonable indexer setup. Reporters are usually willing to > provide their > > log, less often they will do a tracing for you. > > > > > > > > I never thought of the log as something that has to be > meaningful to the > > end user, rather than that for me it is a facility to > collect information > > that can help in resolving issues once they have occurred. > > > > The information is put into the log as information (which > can be filtered > > away) and it is only written, when the index is rebuilt from scratch > > (which should not happen too often). It may be worth > looking into why the > > information is written that often (is the index rebuilt that often?) > > > > > > > > Obviously writing the information to the log can be made > optional. But > > then again the option should be on per default in order to > serve people > > that report problems. > > > > > > > > Markus. > > > > > > > > > > > > > > > > From: cdt-dev-bounces@xxxxxxxxxxx [ > mailto:cdt-dev-bounces@xxxxxxxxxxx ] > > On Behalf Of Alex Blewitt > > Sent: Friday, August 24, 2012 9:09 AM > > To: CDT General developers list. > > Cc: CDT General developers list. > > Subject: Re: [cdt-dev] Indexer polluting the log file > > > > > > > > > > This should really be configurable and disabled by default. > Filling the > > log with cruft doesn't help anyone who is looking after > Eclipse users and > > want to debug different problems where CDT may also be involved. > > > > > > > > > > > > If it's really necessary to know whether an indexer has not > run, maybe > > logging when it fails is more appropriate. But there's a > debug options > > setup that allows you to increase the level of verbosity of > particular > > features - it sounds like that should be used instead of > all the time. > > > > > > > > > > > > Alex > > > > Sent from my iPhone 4S > > > > > > > > On 24 Aug 2012, at 05:54, Yevgeny Shifrin < > Yevgeny.Shifrin@xxxxxxxxxxx > > > wrote: > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > I think that this info is very useful and I am not indexer > developer. > > This way I know that my project was indexed and number of unresolved > > names is reasonable. In my opinion, it should not be changed. > > > > > > > > > > > > Thanks, > > > > > > Yevgeny > > > > > > > > > > > > > > > > From: cdt-dev-bounces@xxxxxxxxxxx [ cdt-dev-bounces@xxxxxxxxxxx ] On > > Behalf Of Doug Schaefer [ dschaefer@xxxxxxx ] > > Sent: Friday, August 24, 2012 4:51 AM > > To: CDT General developers list. > > Subject: Re: [cdt-dev] Indexer polluting the log file > > > > > > > > I find it useful when checking to make sure projects are set up > > correctly. But yeah, there aren't many other features that > add info logs > > in production. > > > > > > > > > > > > BTW, you realize how important the indexer is when it > doesn't work and > > you end up with yellow squiggly lines littered throughout > your source > > code ;) > > > > > > > > > > > > :D > > > > > > > > > > > > From: Mikhail Khodjaiants < mikhailkhod@xxxxxxxxxxxxxx > > > Reply-To: "CDT General developers list." < cdt-dev@xxxxxxxxxxx > > > Date: Thursday, 23 August, 2012 9:18 PM > > To: "CDT General developers list." < cdt-dev@xxxxxxxxxxx > > > Subject: Re: [cdt-dev] Indexer polluting the log file > > > > > > > > > > > > > > > > On 23/08/2012 6:16 PM, Cortell John-RAT042 wrote: > > > > > > > > That said, I'm happy to yield. If others are bothered by > the message, > > they'll speak up J > > > > > > I was very annoyed when this "feature" was added and spoke up but it > > didn't help. > > > > > > > > This e-mail message is intended for the recipient only and contains > > information which is CONFIDENTIAL and which may be > proprietary to ECI > > Telecom. If you have received this transmission in error, > please inform > > us by e-mail, phone or fax, and then delete the original > and all copies > > thereof. > > > > > > > > > > _______________________________________________ > > 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 >
Attachment:
DynamicTrace.png
Description: DynamicTrace.png
