Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Linux Tools Project/0.3 Planning Log
< Linux Tools Project
Revision as of 10:16, 24 April 2009 by Unnamed Poltroon (Talk) (New page: {|border="0" cellpadding="5" cellspacing="0" align="center" |- | '''<overholt> ''' | open OProfile bugs: https://bugs.eclipse.org/bugs/buglist.cg i?query_format=advanced&sh...)
<overholt> | open OProfile bugs: https://bugs.eclipse.org/bugs/buglist.cg i?query_format=advanced&short_desc_type= allwordssubstr&short_desc=&classificatio n=Technology&product=Linux+Tools&compone nt=OProfile&long_desc_type=allwordssubst r&long_desc=&bug_file_loc_type=allwordss ubstr&bug_file_loc=&status_whiteboard_ty pe=allwordssubstr&status_whiteboard=&key words_type=allwords&keywords=&bug_status =UNCONFIRMED&bug_status=NEW&bug_status=A SSIGNED&bug_status=REOPENED&emailtype1=s ubstring&email1=&emailtype2=substring&em ail2=&bugidtype=include&bug_id=&votes=&c hfieldfrom=&chfieldto=Now&chfieldvalue=& cmdtype=doit&order=Reuse+same+sort+as+la st+time&field0-0-0=noop&type0-0-0=noop&v alue0-0-0= | 03:02 |
open Valgrind bugs: https://bugs.eclipse.org/bugs/buglist.cg i?query_format=advanced&short_desc_type= allwordssubstr&short_desc=&classificatio n=Technology&product=Linux+Tools&compone nt=Valgrind&long_desc_type=allwordssubst r&long_desc=&bug_file_loc_type=allwordss ubstr&bug_file_loc=&status_whiteboard_ty pe=allwordssubstr&status_whiteboard=&key words_type=allwords&keywords=&bug_status =UNCONFIRMED&bug_status=NEW&bug_status=A SSIGNED&bug_status=REOPENED&emailtype1=s ubstring&email1=&emailtype2=substring&em ail2=&bugidtype=include&bug_id=&votes=&c hfieldfrom=&chfieldto=Now&chfieldvalue=& cmdtype=doit&order=Reuse+same+sort+as+la st+time&field0-0-0=noop&type0-0-0=noop&v alue0-0-0= | ||
project plan: http://www.eclipse.org/projects/project- plan.php?projectid=technology.linux-dist ros | ||
we have very little in the way of text in the project plan | ||
and I need to fix up the bug queries to make them reflect items planned | 03:03 | |
let's start with you, ksebasti | ||
what do you plan to do for OProfile? | ||
we should collect all items (even long-term ones) in bugzilla | ||
then prioritize per milestone/release | 03:04 | |
so let's file some | ||
<ebaron> | sounds good | |
<overholt> | and look at the open ones | |
<ksebasti> | well after the user guide im doing now (which i think is looking pretty good :D http://wiki.eclipse.org/Linux_Tools_Proj ect/OProfile/User_Guide) | |
<overholt> | :) | |
and that's bug ~272039 | ||
<KOS-MOS> | Bug 272039 - https://bugs.eclipse.org/bugs/show_bug.c gi?id=272039 - Linux Tools / OProfile / unspecified - All / All - NEW / normal / - Assignee: ksebasti@redhat.com - Write OProfile plugin user documentation | |
<ksebasti> | i plan to start on ~265794 | |
<KOS-MOS> | Bug 265794 - https://bugs.eclipse.org/bugs/show_bug.c gi?id=265794 - Linux Tools / OProfile / unspecified - PC / Linux - NEW / enhancement / - Assignee: ksebasti@redhat.com - OProfile: Start/Stop profiling manually or after given duration | |
<overholt> | okay | |
jjohnstn: akurtakov_: others who may be interested: we'd love to hear your thoughts on these things | 03:05 | |
crazy ideas welcome :) | ||
<ksebasti> | because i can see it poking in many areas, and would make the plugin much more useful | |
<overholt> | ok | |
<ksebasti> | also add some tests to the launch plugin.. | |
<overholt> | okay | |
we can file these bugs afterwards | 03:06 | |
let's just talk here | ||
<ksebasti> | they were mysteriously absent :) | |
<overholt> | heh | |
what about the hot spot colourization? | ||
<ksebasti> | indeed that could probably make it too | |
<overholt> | okay | |
<ksebasti> | because theres already some code in a branch that didnt make it for 0.2 | 03:07 |
but id rather have it at a lower priority than the start/stop feature | ||
<overholt> | so for 0.3 OProfile we have: colourize hot spots, write documentation, and make the profiling manually controllable | |
so the latter two for sure | ||
<ksebasti> | because its a nicety rather than a functionality thing | |
<overholt> | the first one maybe | |
okay with me | ||
anyone else have an opinion? | ||
<ksebasti> | oh the documentation should be done reasonably soon.. its already been a good chunk of days :p | |
<overholt> | ok | 03:08 |
<ebaron> | looks good to me | |
<jjohnstn> | overholt: unfortunately I haven't played with the OProfile plugin to have any meaningful comments....I could review the user doc though | |
<overholt> | jjohnstn: that's cool. what about general profiling features you'd liek to see? | |
<ksebasti> | also ~273116 but thats just a small bug which im pretty sure is a 1-2 line fix | |
<KOS-MOS> | Bug 273116 - https://bugs.eclipse.org/bugs/show_bug.c gi?id=273116 - Linux Tools / OProfile / unspecified - PC / Linux - NEW / normal / - Assignee: ksebasti@redhat.com - vmlinux text box not repopulated | |
<overholt> | with gprof coming in, we'll have to think about how to make it as general as possible | |
ksebasti: ok, we'll leave that targetted at 0.3 | 03:09 | |
anything else for OProfile in 0.3? Early July is the target release date for 0.3. | ||
<ksebasti> | later in the cycle when policy kit 1 is out perhaps poke into ~265646 | 03:10 |
<KOS-MOS> | Bug 265646 - https://bugs.eclipse.org/bugs/show_bug.c gi?id=265646 - Linux Tools / OProfile / unspecified - PC / Linux - NEW / normal / - Assignee: ksebasti@redhat.com - Find better way to do non-root opcontrol invocation across distros | |
<ksebasti> | and at some point i'd like to clean up (in the most general sense :-) the opxml code for future maintainers | 03:11 |
and see how much of it could perhaps be used from oprofile xml output | ||
and otherwise poke upstream | ||
whoo 0.3 is gonna be fun ;) | ||
<overholt> | :) | |
so realistically we're looking at ~272039, ~273116, and ~265646 | 03:12 | |
<KOS-MOS> | Bug 265646 - https://bugs.eclipse.org/bugs/show_bug.c gi?id=265646 - Linux Tools / OProfile / unspecified - PC / Linux - NEW / normal / - Assignee: ksebasti@redhat.com - Find better way to do non-root opcontrol invocation across distros | |
<overholt> | documentation, small vmlinux fix, and start/top daemon | |
<rcjsuen> | overholt: Punctuation bug still in place. ~272039 ~273116 | |
<KOS-MOS> | Bug 272039 - https://bugs.eclipse.org/bugs/show_bug.c gi?id=272039 - Linux Tools / OProfile / unspecified - All / All - NEW / normal / - Assignee: ksebasti@redhat.com - Write OProfile plugin user documentation | |
Bug 273116 - https://bugs.eclipse.org/bugs/show_bug.c gi?id=273116 - Linux Tools / OProfile / unspecified - PC / Linux - NEW / normal / - Assignee: ksebasti@redhat.com - vmlinux text box not repopulated | ||
<overholt> | rcjsuen: thanks | 03:13 |
<ksebasti> | thats definitely doable | |
<overholt> | ksebasti: when the gprof contribution is cleared by legal we'll have to look at integrating that | |
okay, great | ||
unless anyone else has thoughts about OProfile, we can move on to Valgrind | ||
<ksebasti> | im inclined to add ~249181 because i expect the first 2 to not take very long | |
<KOS-MOS> | Bug 249181 - https://bugs.eclipse.org/bugs/show_bug.c gi?id=249181 - Linux Tools / OProfile / unspecified - PC / Linux - NEW / enhancement / - Assignee: ksebasti@redhat.com - Colourize hot spots in code | |
<overholt> | ksebasti: let's try to get it in but not put the milestone on. and let's leave it until the other things are done | 03:14 |
<ksebasti> | overholt, righto | |
<overholt> | as usual, if people have bugs or RFEs or whatever, file away | |
thanks, ksebasti | ||
ebaron: let's move on to Valgrind | ||
ebaron: https://bugs.eclipse.org/bugs/buglist.cg i?query_format=advanced&short_desc_type= allwordssubstr&short_desc=&classificatio n=Technology&product=Linux+Tools&compone nt=Valgrind&long_desc_type=allwordssubst r&long_desc=&bug_file_loc_type=allwordss ubstr&bug_file_loc=&status_whiteboard_ty pe=allwordssubstr&status_whiteboard=&key words_type=allwords&keywords=&bug_status =UNCONFIRMED&bug_status=NEW&bug_status=A SSIGNED&bug_status=REOPENED&emailtype1=s ubstring&email1=&emailtype2=substring&em ail2=&bugidtype=include&bug_id=&votes=&c hfieldfrom=&chfieldto=Now&chfieldvalue=& cmdtype=doit&order=Reuse+same+sort+as+la st+time&field0-0-0=noop&type0-0-0=noop&v alue0-0-0= | 03:15 | |
<ebaron> | overholt, thanks | |
overholt, ~272198 should be resolved now | ||
<overholt> | ebaron: all of those except "Investigate CDT Debug integration" have a target of 0.3. | |
<KOS-MOS> | Bug 272198 - https://bugs.eclipse.org/bugs/show_bug.c gi?id=272198 - Linux Tools / Valgrind / unspecified - All / All - NEW / normal / - Assignee: ebaron@redhat.com - Binary for test project does not always get built | |
<overholt> | ebaron: sweet! | |
ebaron: is cachegrind mostly done? | 03:16 | |
<ebaron> | overholt, yes | |
<overholt> | ebaron: what's up next? | |
<ebaron> | overholt, i was looking into birt charting, but that's more of a callgrind feature | |
for call graphs and such | ||
<overholt> | ok | |
<ebaron> | overholt, so long term, we'll have callgrind and helgrind support | |
<overholt> | okay | 03:17 |
could one of them get into 0.3? | ||
<ebaron> | overholt, i feel there are more pressing things to take care of | |
overholt, ~272035 | ||
<KOS-MOS> | Bug 272035 - https://bugs.eclipse.org/bugs/show_bug.c gi?id=272035 - Linux Tools / Valgrind / unspecified - All / All - NEW / normal / - Assignee: ebaron@redhat.com - Guard against segfaults of inferior program | |
<overholt> | ebaron: okay | |
<ebaron> | overholt, this issue brought the limitations of valgrind's xml output to my attention | |
<overholt> | ebaron: alright | 03:18 |
<ebaron> | i took a look at how other valgrind GUIs handle errors of this kind | |
<overholt> | yeah, that'd be interesting | |
so that + documentation | ||
anything new in Valgrind 3.4.0 that we need to support? | ||
<ebaron> | valgrind actually does have good signal handling, but this does not get reported with XML output | |
<overholt> | ah | |
<ebaron> | overholt, just a few new options | 03:19 |
<overholt> | could that make 0.3? or is it a non-issue? | |
<ebaron> | overholt, i think moving away from xml output would be beneficial | |
<overholt> | ok | |
will it be as parseable | ||
? | ||
<ebaron> | overholt, yeah 3.4.0 options for sure can make it in, i've already implemented the code for version checking | 03:20 |
<overholt> | sweet | |
<ebaron> | overholt, it is parseable | |
<overholt> | alright | |
<ebaron> | alleyoop is one example of a GUI that doesn't use the xml output | |
<overholt> | okay. I guess we should do some smoke testing with galileo stuff for 0.3, too | 03:21 |
<ebaron> | valkyrie, the "official" GUI for valgrind does use xml, but doesn't report segfaults or other kinds of errors | |
<overholt> | ksebasti: that goes for you, too. we're running builds against galileo deps but doing some smoke tests would be good. | |
ebaron: ok | ||
so we can target 0.4 for callgrind or helgrind (whichever comes first)? | ||
<ebaron> | overholt, sure | |
overholt, callgrind would come first | 03:22 | |
<overholt> | and 0.3 for Valgrind can kind of be some further robustification | |
+ docs + Valgrind 3.4.0 support | ||
+ the fix for ~272198 | ||
<KOS-MOS> | Bug 272198 - https://bugs.eclipse.org/bugs/show_bug.c gi?id=272198 - Linux Tools / Valgrind / unspecified - All / All - NEW / normal / - Assignee: ebaron@redhat.com - Binary for test project does not always get built | |
<overholt> | that works for me | |
then 0.3's work is predictable and you will hopefully have time for 0.4-targeted features | ||
<ebaron> | overholt, i think it's important since most people use memcheck, i want to ensure it works perfectly | |
<overholt> | agreed | 03:23 |
I'm going to guess no one else have any opinions | ||
<jjohnstn> | I don't | |
<overholt> | okay | |
s/have/has | ||
I'll post this log somewhere and send the link to the mailing list | 03:24 | |
people may come out of the woodwork with bugs then | ||
I'm sure we'll have bugs filed once 0.2 is out, too | ||
***ksebasti | thinks ebaron should add a remix feature to his plugin ;) | |
<overholt> | a remix feature? | |
<ksebasti> | virtual turntables and all! | |
</joke> | ||
<overholt> | ah | |
for sure! | 03:25 | |
<ebaron> | :D | |
<overholt> | well, we're only 30 minutes into our hour. we could discuss some other sub-projects | |
jjohnstn: we should file some bugs for your work re-writing the autotools builder | ||
<jjohnstn> | overholt: ok | |
<overholt> | akurtakov_: for 0.3 we'll try to ship eclipse-build in some form? | |
jjohnstn: any plans for ChangeLog or libhover in 0.3? | ||
pmuldoon: I don't know if you're around, but Anithra has been approved as a committer and will likely start working directly in SVN soon | 03:26 | |
<akurtakov_> | overholt: do we require it to produce a working eclipse for the release | |
<overholt> | pmuldoon: we should look at integrating your editor with the rest of the SystemTapGUI stuff | |
akurtakov_: I wonder if that should be the demarcation point where we release it for the first time? | 03:27 | |
<jjohnstn> | overholt: I would like to push libhover C++ and newlib for 0.3...for changelog I would like to take a look at an annoying CTRL+ALT+P bug | |
<overholt> | jjohnstn: okay, sounds good | |
<akurtakov_> | overholt: well, before this point we actually have nothing :) | |
<overholt> | akurtakov_: do you anticipate that happening in the next 8 weeks? | |
<akurtakov_> | overholt: at least a partially working sdk yes | 03:28 |
<overholt> | akurtakov_: okay, well let's aim for that | |
<akurtakov_> | overholt: i mean builds and starts but don't know what happens after that | |
:) | ||
<overholt> | I'll file bugs for all of this stuff | |
akurtakov_: sure :) | ||
akurtakov_: any big plans for .spec editor? | ||
people asked for ability to build RPMs when I presented at EclipseCon | 03:29 | |
we should ensure we have bugs filed so people can hop on if they're interested | ||
I'll do a big triage | ||
<akurtakov_> | overholt: using rpmbuild? | |
<overholt> | akurtakov_: yeah | |
on another distro-related note, I'd had a bit of time to look at running the SDK tests against an installed set of packages | ||
<akurtakov_> | overholt: i should take a look at the old plugins whether there is smth about building | 03:30 |
<overholt> | I'd love to see if we get similar results on another distro -- preferably non-RPM -- but that'll take some coercion I expect :) | |
akurtakov_: yeah, we should see if we can use any of that code | ||
akurtakov_: perhaps target 0.4 with some rudimentary RPM building | ||
not 0.3 | ||
if anyone notices, I'm being conservative with estimates here | ||
I want our project to be predictable as much as possible | 03:31 | |
hopefully that will get us some more contributors | ||
or at the very least adopters | ||
the Ericsson guys are going to start work on their tracing stuff soon, I expect | ||
they were talking about it at EclipseCon | 03:32 | |
<akurtakov_> | overholt: i still want to get a form based editor but eclipse-build is taking my time | |
<jjohnstn> | overholt: was there ever a feature opened to make the rpm spec editor a RCP application? | |
<overholt> | akurtakov_: yeah, a form-based editor would be cool | |
jjohnstn: no, but that' s a neat idea | ||
I don't think the non-RPM-based distros are ready for something like stubby yet, but it would be neat. maybe after akurtakov_ & co. have eclipse-build out there, more distros will pick it up | 03:33 | |
then they'll be at the stage of packaging other plugins | ||
I'm going to write a little bit of "getting started" text for people not familiar with Eclipse plugin installation | ||
oh, and the gprof contribution is undergoing legal review | 03:34 | |
but that'll hopefully be finished soon | ||
then Xavier & co. can work in SVN | ||
maybe that can make 0.3, actually | 03:35 | |
<akurtakov_> | exherbo packaging file is quite similar in structure to spec file | |
<overholt> | I played around with it | |
akurtakov_: I'm not familiar with exherbo | ||
<akurtakov_> | so stubby would fit for them nicely | |
<overholt> | that's good | |
the gprof plugin as it stands opens up gprof output files | ||
I'd love to see a standard way of using various profiling "backends" | ||
ksebasti: does post-processing analysis make sense for OProfile? | ||
<ksebasti> | what sort of post processing? | 03:36 |
<overholt> | ksebasti: like saving the output in a file or something and then opening it up with an Eclipse view | |
I guess I meant post-execution analysis | ||
I guess that's what we do now | ||
<ksebasti> | the sample files are generated by oprofile and already there | 03:37 |
<overholt> | I guess gprof doesn't do that | |
we'll have to see where things overlap and where they differ | ||
I don't really have anything else to talk about | ||
our 0.2 release is scheduled for review on May 6th | 03:38 | |
the slides are done and so's the N&N thanks to everyone | ||
our builds are now producing p2 repositories | ||
updates-nightly gets updated automatically with these | ||
you may notice there's no site.xml anymore | ||
that's because p2 repositories use content.jar (which is basically just a zip of content.xml) | 03:39 | |
oh, and we're down to 0 warnings | ||
<jjohnstn> | cool | |
<overholt> | thanks for the work there, jjohnstn | |
<jjohnstn> | np | |
<overholt> | Hudson on build.eclipse.org is accessible to all | |
you can use your committer username/password to log in | ||
I think I set everyone to have the permission to start builds | ||
they happen automatically every 6 hours | 03:40 | |
i think that's all I have to say | ||
anyone else? | ||
<jjohnstn> | not me | |
<overholt> | ebaron: ksebasti: akurtakov_: you all okay for 0.3? I'll file bugs and send some follow-up mail | 03:41 |
<ksebasti> | all good | |
<overholt> | giddy-up | |
<ebaron> | overholt, sounds good, i'm sure things will come up, but that's a good start | |
<akurtakov_> | yep, 0.3 for me is get eclipse-build as much as possible ready :) | |
<ksebasti> | overholt, im filing some bugs i just thought of though :) | |
<overholt> | ksebasti: thanks | |
akurtakov_: great, looking forward to it! | ||
alright, thanks for taking the time to talk, everyone. next time I'll bill it as a "project meeting" so others may be more interested in attending :) | 03:42 |