On 19.02.2014 11:38, Yuan Pengfei wrote: > Using -fprofile-values is one case that will cause the memory allocation > problem. More changes are needed to fully support -fprofile-values. I > submit this patch first because I think it is obvious and does no harm. >> I'm unaware of any user of -fprofile-values in the kernel. Are you >> trying to extend gcov-kernel to also support -fprofile-values? I would >> expect that additional changes to the .gcda file creation logic are >> required to fully support this GCC option.
If there is a way to trigger the problem of gcov_info.values == NULL using the existing gcov-kernel infrastructure then I agree that this should be fixed. If not, then I would rather see the suggested change as part of a patch series that enables other profiling types. -- Peter Oberparleiter Linux on System z Development - IBM Germany -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
