The error message encountered when kernel_config[CONFIG_UTRACE] != "y" could mention the possibility that kernel development headers are not installed. I have attached a suggested quick-fix. If the CONFIG_UTRACE is blank, the semantic error will prompt the user to check that devel headers are installed. e.g.: semantic error: process probes unavailable without kernel CONFIG_UTRACE, ensure kernel devel headers are installed and CONFIG_UTRACE is enabled while resolving probe point process("/home/chwang/runtime-EclipseApplication/CallGraphDemo/Debug/eag").function("*").call
Created attachment 4558 [details] Suggested patch for 11229 Just makes a minor adjustment to the error messages... I was unable to disable CONFIG_UTRACE in my kernel (only remove kernel-devel) so I am not sure if CONFIG_UTRACE == "" is a valid check for CONFIG_UTRACE disabled vs. kernel-devel not installed -- in the worst case scenario the longer error message will display in both cases.
Probably what it should do is if it gets any kind of "need CONFIG_*" kind of situation, it should fall back to some more thorough basic sanity tests. Then it can figure out if e.g. it's impossible to build any module at all, and report about that more clearly.
CONFIG_UTRACE is not special in this respect. We already have some heuristics that try to warn users of an inadequate installation of kernel-devel. Perhaps those heuristic messages can instead be printed when we try to inhale the kernel_config[] list.
I want to just add that the error message shown is really confusing and made me think that the problem was elsewhere(Eclipse callgraph plugin). From the given error message there was no clue what went wrong once you see that your kernel is compiled with CONFIG_UTRACE.
Created attachment 4563 [details] Suggested patch for 11229 Naive implementation of Frank's suggestion with the heuristics -- changes parse_kernel_config from void to int. Returns non-zero if the kernel_config file cannot be found. With kernel-devel removed: Checking "/lib/modules/2.6.31.12-174.2.3.fc12.x86_64/build/.config" failed: No such file or directory Ensure kernel development headers & makefiles are installed. I don't have a kernel without CONFIG_UTRACE configured and I'm not sure atm how to do this, but I will if you think I should proceed with testing. -Charley
(In reply to comment #5) > Created an attachment (id=4563) > Suggested patch for 11229 Looks good to me, please commit & close this bug.
Committed just now