Community
Participate
Working Groups
The GProf plugins produce 18 compiler warnings. They can be seen here: https://build.eclipse.org/hudson/job/cbi-linuxtools-Galileo/297/warningsResult/ Prior to adding these plugins to the build we had a warning-free build. I'd like to get back to that if possible :)
Try to fix for 0.4 release.
Xavier, I'd like to add the GProf plugins to our nightly builds. Are you able to track down these compiler warnings? I can run a new build showing them if you'd like.
I'm going to add the tests to the automated build so fixing this will become more time-sensitive :) Building locally may help reproduce the problem if you can't do it from within Eclipse. Other project committers have gone through local build test failure diagnosing and may be able to help. This wiki page may also be of help: http://wiki.eclipse.org/Linux_Tools_Project/Releng#Building_locally
Hi andrew, As you probably noticed, only 3 warnings are remaining in gprof. However, I do not know how to fix them for now. These warnings occurs, because gprof uses an internal CDT API, required for link-to-source support. I do not know how to workaround that. I guess I have to open a request on CDT tracker ?
(In reply to comment #4) > > As you probably noticed, only 3 warnings are remaining in gprof. Yes, that's great! Thanks for fixing the others. > These warnings occurs, because gprof uses an internal CDT API, required for > link-to-source support. Our OProfile, Valgrind, and Callgraph (under systemtap in SVN) functionality also has link-to-source support and doesn't need to use internal APIs AFAIK. Maybe look at that code? > I do not know how to workaround that. I guess I have to open a request on CDT > tracker ? Obviously use of internals is discouraged, but if it can't be avoided, yes, requesting API from the CDT team is best. Jeff, how did you avoid warnings in cases like this in the past?
Let's see if we can clean these up for 0.5.
Question send to CDT mailing list: http://dev.eclipse.org/mhonarc/lists/cdt-dev/msg16774.html
DSF has the same issue: - https://bugs.eclipse.org/bugs/show_bug.cgi?id=235181 - https://bugs.eclipse.org/bugs/show_bug.cgi?id=159952
Removing target milestone of 0.5 for bugs that won't make it for 0.5.
Updating Xavier's email address for existing bugs.
What's the state on this bug?
I've just checked on Juno-M5. No change since Helios.
(In reply to comment #12) > I've just checked on Juno-M5. > No change since Helios. Can you ask again on cdt-dev, Xavier?
What's the status 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. -- The automated Eclipse Genie.
Let's close the bug. Codebase changed a lot and the original link is no longer there.
