Re: Build failures: unresolved symbol vfs_getattr

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Sep 16, 2020 at 11:06:27AM +0200, Jiri Olsa wrote:
> On Tue, Sep 15, 2020 at 02:17:46PM +0200, Jiri Olsa wrote:
> 
> SNIP
> 
> > 	 <2><140d7aa>: Abbrev Number: 3 (DW_TAG_formal_parameter)
> > 	    <140d7ab>   DW_AT_type        : <0x140cfb6>
> > 	 <2><140d7af>: Abbrev Number: 3 (DW_TAG_formal_parameter)
> > 	    <140d7b0>   DW_AT_type        : <0x1406176>
> > 	 <2><140d7b4>: Abbrev Number: 3 (DW_TAG_formal_parameter)
> > 	    <140d7b5>   DW_AT_type        : <0x14060c9>
> > 	 <2><140d7b9>: Abbrev Number: 0
> > 
> > the latter is just declaration.. but it's missing the
> >     <365d69d>   DW_AT_declaration : 1
> > 
> > so it goes through pahole's function processing:
> > 
> > 	cu__encode_btf:
> > 	...
> >         cu__for_each_function(cu, core_id, fn) {
> >                 int btf_fnproto_id, btf_fn_id;
> > 
> >                 if (fn->declaration || !fn->external)
> >                         continue;
> > 	...
> > 
> > 
> > CC-ing Frank.. any idea why is the DW_AT_declaration : 1 missing?
> 
> looks like gcc issue:
>   https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97060
> 
> let's see ;-)

so this gcc bug did not disappear and the fix might be delayed,
as I was told it's real complex and difficult to fix

and it's no longer just rawhide issue, because I just started to
see it in Fedora 32 after updating to gcc (GCC) 10.2.1 20201005
(Red Hat 10.2.1-5)

I'm checking on pahole's workaround, but so far I can't see dwarf
based solution for that.. any thoughts/ideas? ;-)

thanks,
jirka




[Index of Archives]     [Linux Samsung SoC]     [Linux Rockchip SoC]     [Linux Actions SoC]     [Linux for Synopsys ARC Processors]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]


  Powered by Linux