Community
Participate
Working Groups
User picks two events and clicks "Compare Each Other" from popup menu. We could either reuse Compare stuff and show text diffefences, or utilize new event details editor (bug 217644) and compare events more structurally (session/event details/stack trace). I always grudged Compare team their neat "Compare with -> Each Other" thing. (http://eclipser-blog.blogspot.com/2007/07/compare-folders-on-windows.html)
...later we could compare log sessions
now we're getting fancy and possibly competing with TPTP :)
see: https://bugs.eclipse.org/bugs/show_bug.cgi?id=217644#c10 ok it's wrong way :) I think what we need is Eclipse logs adapter for TPTP stuff. They have defaults for Apache, and few others...
adding Alex from TPTP, who declared to comment eventual impl. and suggested to place this in TPTP.
Created attachment 91994 [details] first shot Attached is project to be imported to Eclipse with static log adapter for Eclipse .log files. It's early version, so what works: - session, entry, subentry elements are processed with most of their attributes. - importing a .log file using TPTP's "Import... -> Log file" - correlating two or more .log files by time What doesn't work - session attributes (like eclipse.buildId, java.fullversion, etc.) are not read - but that's simple - when Parser calls readALine() for first time, it always gets a string composed of ~65000 zeros, like [0,0,0,0,0,0......] - but it looks like TPTP issue (I use 4.3.0) - associations between events don't work, however I don't know why yet. When processing a Session, I cache it in parser local field. In next parseEvent() call, during processing Entry, I do following to add this entry to cached session: session.addAssociatedEvent("pde_log", AssociationEngine.TYPE_CONTAIN, Guid.generate(), new String[] {event.getGlobalInstanceId() } ); which seems to work, but later in Log View, I don't see these associations.
Created attachment 91995 [details] log_grammar Simple .log file grammar for reference. Eclipse log is generated by org.eclipse.core.runtime.adaptor.EclipseLog class.
Created attachment 91996 [details] screenshot here's how it looks like....
so next steps: I'll keep testing and improving adapter usability but all your comments are welcome :)
Jacek, you want us to test with the code in comment #5 ?
(In reply to comment #9) > Jacek, you want us to test with the code in comment #5 ? sure, give it a try. I'm all ears to your comments.
*** Bug 234150 has been marked as a duplicate of this bug. ***
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
Please remove the stalebug flag, if this issue is still relevant and can be reproduced on the latest release.
