This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
RE: [RFC] Send new ARI warnings to gdb_testers mailing list
- From: "Pierre Muller" <muller at ics dot u-strasbg dot fr>
- To: "'Joel Brobecker'" <brobecker at adacore dot com>
- Cc: <gdb-patches at sourceware dot org>
- Date: Wed, 6 May 2009 18:45:51 +0200
- Subject: RE: [RFC] Send new ARI warnings to gdb_testers mailing list
- References: <001801c9c397$0e35ba90$2aa12fb0$@u-strasbg.fr> <20090423184213.GE7552@adacore.com> <013401c9ca3e$852e58c0$8f8b0a40$@u-strasbg.fr> <20090506163051.GL10734@adacore.com>
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