Bugzilla – Full Text Bug Listing
| Summary: | Provide some hints in order to be able to determine cause of opaque bugs | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Severin Gehwolf <sgehwolf> | ||||||
| Component: | LinuxTools | Assignee: | Severin Gehwolf <sgehwolf> | ||||||
| Status: | CLOSED FIXED | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | P3 | CC: | kksebasti, linux.oprofile-inbox, overholt | ||||||
| Version: | unspecified | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | PC | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
I like the intent. Can we put it in some sort of -debug output that is controlled with a .options file like the p2 diagnostics? Created attachment 197234 [details]
Print more verbose messages if debugging is turned on.
Thanks, Andrew. How about this? Now, it only prints those messages if eclipse is started with -debug and some .options file (either in $(pwd)/.options or $HOME/.options) has:
org.eclipse.linuxtools.oprofile.core/debug
in it.
It looks good! +1 to commit now as it will help us sort out OProfile issues. Thanks Andrew! Pushed: 34770cc454334dd8d600690417f9a18f46aed97c |
Created attachment 197186 [details] Proposed patch When calling out to opcontrol it's a good idea to print what's going on on stderr/stdout of the sub-process. It may provide hints as to what is *really* going wrong. Andrew, could you have a look?