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: [RFC] Send new ARI warnings to gdb_testers mailing list


Here is an update on this issue.

 Since I added this feature, I received 6 emails.
2 of them where due to the 6.8 branch
that got additional warnings due to my changes to gdb_ari.sh
1 email was about more use of gdbarch methods, which of course
is not of interest here.

I improved the checks about failure in update-web-ari
1) I removed all gdbarch category warnings, as they are not 
relevant here.
2) I used sed to replace the lines with zero'ed line numbers
by the original lines of the gdb_ari.sh script.

The last email I got is this:

>>>>>>>>>> Email Title
ARI warning list change Tue May 19 01:55:11 UTC 2009
>>>>>>>>>> Start of email body
1049a1046,1047
> gdb/lm32-tdep.c:293: deprecate: write_memory: Replace write_memory() with
regcache_read() et.al.
> gdb/lm32-tdep.c:337: deprecate: read_memory: Replace read_memory() with
regcache_read() et.al.
58,59d57
< gdb/doublest.h:96: deprecated: deprecated extract_floating: Do not use
deprecated extract_floating, see declaration for details 
< gdb/doublest.h:97: deprecated: deprecated store_floating: Do not use
deprecated store_floating, see declaration for details 
106d103
< gdb/ada-lang.c:1695: deprecated: deprecated set_value_type: Do not use
deprecated set_value_type, see declaration for details
163d159
< gdb/sh64-tdep.c:1580: deprecated: deprecated extract_floating: Do not use
deprecated extract_floating, see declaration for details
1600,1601d1597
< gdb/doublest.c:822: deprecated: deprecated extract_floating: Do not use
deprecated extract_floating, see declaration for details 
< gdb/doublest.c:839: deprecated: deprecated store_floating: Do not use
deprecated store_floating, see declaration for details
>>>>>>>>>> End of email

Should I change the email address to gdb-testers?

Pierre Muller
trying to improve ARI stuff.


> -----Message d'origine-----
> De?: gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Pierre Muller
> Envoyé?: Wednesday, May 06, 2009 6:46 PM
> À?: 'Joel Brobecker'
> Cc?: gdb-patches@sourceware.org
> Objet?: RE: [RFC] Send new ARI warnings to gdb_testers mailing list
> 
> I just committed this with my email address
> and will inform you of the first results I get.
> 
> Pierre
> 
> > -----Message d'origine-----
> > De?: Joel Brobecker [mailto:brobecker@adacore.com]
> > Envoyé?: Wednesday, May 06, 2009 6:31 PM
> > À?: Pierre Muller
> > Cc?: gdb-patches@sourceware.org
> > Objet?: Re: [RFC] Send new ARI warnings to gdb_testers mailing list
> >
> > > The only drawback is that the line number also does not appear
> > > on the generated email...
> >
> > Initially, I thought that this was a pretty significant drawback.
> > But I tried to come up with a way of isolating the new line, and
> > I'm not sure whether this is possible or not. The problem is that
> > the line number associated to an error/warning can change from
> > day to day, as we modify the source around it.
> >
> > We could try your current approach, and see if that helps or not...
> > Why not activating your change, but with yourself as the the only
> > recipient, as opposed to gdb-testers? That will allow you to
> determine
> > the frequency of such messages, as we as how difficult it is to
> > determine which entry is the new one...
> >
> > --
> > Joel


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