Re: [PATCH] gcov: fix memory allocation problem in gcov_info_dup

2014-02-20 Thread Peter Oberparleiter
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 -fprofi

Re: [PATCH] gcov: fix memory allocation problem in gcov_info_dup

2014-02-19 Thread Yuan Pengfei
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 ext

Re: [PATCH] gcov: fix memory allocation problem in gcov_info_dup

2014-02-19 Thread Peter Oberparleiter
On 19.02.2014 08:06, Yuan Pengfei wrote: > From: Yuan Pengfei > > If -fprofile-values option is used, ctr->num and sci_ptr->num > may be zero, resulting in zero size and cv_size, which will > cause ENOMEM when opening gcov data files in debugfs. > Signed-off-by: Yuan Pengfei I'm unaware of any

[PATCH] gcov: fix memory allocation problem in gcov_info_dup

2014-02-18 Thread Yuan Pengfei
From: Yuan Pengfei If -fprofile-values option is used, ctr->num and sci_ptr->num may be zero, resulting in zero size and cv_size, which will cause ENOMEM when opening gcov data files in debugfs. Signed-off-by: Yuan Pengfei --- kernel/gcov/gcc_3_4.c | 2 +- kernel/gcov/gcc_4_7.c | 2 +- 2 files