Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <mec@shout.net>
To: drow@mvista.com, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Fix watchpoints when stepping over a breakpoint
Date: Tue, 02 Apr 2002 22:18:00 -0000	[thread overview]
Message-ID: <200204030618.g336In527476@duracef.shout.net> (raw)

My test bed says: no significant changes.

  target  = native
  host    = i686-pc-linux-gnu%rh-7.2
  gdb     = HEAD%20020331 + drow infrun.c
  gcc     = 2.95.3, vendor, 3.0.4, gcc-3_1-branch%20020331, HEAD%20020331
  glibc   = vendor
  goption = -gdwarf-2, -gstabs+

I'm not qualified to give an opinion on infrun.c changes, but I can say
that this one don't break anything on native i686-pc-linux-gnu.

I also note that there is an insignificant change in this test:

  gdb.c++/annota2.exp: annotate-quit

This test is unstable and changes a lot, even on identical back-to-back runs.
Auspiciously all of the noise on this comparison was FAIL->PASS noise but
it's probably meaningless.

Michael C


             reply	other threads:[~2002-04-03  6:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-02 22:18 Michael Elizabeth Chastain [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-02 15:43 Daniel Jacobowitz
2002-04-04 23:38 ` Eli Zaretskii
2002-04-05  7:54   ` Daniel Jacobowitz
2002-04-05  8:45     ` Eli Zaretskii
2002-04-05  9:08       ` Daniel Jacobowitz
2002-04-05  9:55         ` Andrew Cagney
2002-04-05 23:48         ` Eli Zaretskii
2002-04-06  7:36           ` Daniel Jacobowitz
2002-04-06  9:21             ` Eli Zaretskii
2002-04-06  9:49               ` Daniel Jacobowitz
2002-04-07  9:16                 ` Andrew Cagney
2002-04-07 10:03                   ` Eli Zaretskii
2002-04-14 14:49                     ` Andrew Cagney
2002-04-14 22:07                       ` Eli Zaretskii
2002-04-18 18:34                         ` Andrew Cagney

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=200204030618.g336In527476@duracef.shout.net \
    --to=mec@shout.net \
    --cc=drow@mvista.com \
    --cc=gdb-patches@sources.redhat.com \
    /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