This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: New ARI warning Thu Apr 18 01:51:12 UTC 2013 in -D 2013-04-18-gmt



> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Joel Brobecker
> Envoyé : jeudi 18 avril 2013 17:17
> À : GDB Administrator
> Cc : gdb-patches@sourceware.org
> Objet : Re: New ARI warning Thu Apr 18 01:51:12 UTC 2013 in -D 2013-04-18-
> gmt
> 
> > > gdb/dwarf2read.c:17927: code: editCase function: Function name starts
> lower case but has uppercased letters.
> > gdb/dwarf2read.c:17927:get_DW_AT_signature_type (struct die_info *die,
> struct attribute *attr,			  struct dwarf2_cu *cu)
> 
> Let's add an ARI marker to accept this as a valid exception...
I agree in principle,
but the problem is that to avoid the warning you should add 
/* ARI: editCase */ comment...
And the natural position to insert such comment would 
be after the closing brace of the parameter list.
As you can see above, the function header of get_DW_AT_signature_type is
already
on two lines...

But comments are handled early in gdb_ari.sh gawk script,
as all comments are removed later on.
But this means that it would be difficult to parse multilines
for this ARI comment...

  To put it bluntly,
once again my AWK level is too low to fix this kind of issues...

Pierre Muller
as not-efficient ARI maintainer



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]