From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'Pierre Muller'" <muller@ics.u-strasbg.fr>,
"'Joel Brobecker'" <brobecker@adacore.com>
Cc: <gdb-patches@sourceware.org>
Subject: RE: [RFC] Send new ARI warnings to gdb_testers mailing list
Date: Tue, 19 May 2009 08:35:00 -0000 [thread overview]
Message-ID: <001001c9d85c$940312b0$bc093810$@u-strasbg.fr> (raw)
In-Reply-To: <001d01c9ce6a$1d6d7e20$58487a60$@u-strasbg.fr>
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
next prev parent reply other threads:[~2009-05-19 8:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 22:10 Pierre Muller
2009-04-23 18:42 ` Joel Brobecker
2009-05-01 9:24 ` Pierre Muller
2009-05-06 16:31 ` Joel Brobecker
2009-05-06 16:46 ` Pierre Muller
2009-05-19 8:35 ` Pierre Muller [this message]
2009-05-20 5:23 ` Joel Brobecker
2009-10-08 11:15 ` Pierre Muller
2009-10-08 15:52 ` Joel Brobecker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='001001c9d85c$940312b0$bc093810$@u-strasbg.fr' \
--to=muller@ics.u-strasbg.fr \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox