Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pierre Muller <muller@cerbere.u-strasbg.fr>
To: gdb-patches@sources.redhat.com
Subject: Re: [RFC/RFA] Add hardware watchpoint support for cygwin target.
Date: Mon, 10 Dec 2001 02:23:00 -0000	[thread overview]
Message-ID: <4.2.0.58.20011210111416.013e24f0@ics.u-strasbg.fr> (raw)
In-Reply-To: <20011208005809.GB27247@redhat.com>

At 01:58 08/12/2001 , Christopher Faylor a écrit:
>On Thu, Dec 06, 2001 at 09:37:23AM +0100, Pierre Muller wrote:
> >This is probably an UI_OUT specific problem, but as its again not
> >cygwin specific I don't think that there is any reason to delay
> >approval.
>
>Have we seen independent corroboration of the bugs that you reported?

I am not sure I understand your question.

   Do you ask if someone else saw this unwanted 'Hardware watchpoint : ....'
messages. I don't know, nobody explicitly did respond to the messages
by saying that this is indeed the case, but the way to reproduce them
is quite straight forward:

   Compile gdb 5.1 from FSF sources,
run
   ./gdb ./gdb 
from the build/gdb dir.
add a hardware watchpoint at gdb_stdlog for instance with
'top-gdb>watch gdb_stdlog'
and run simply with
'run'

This gave me several print out of  the 'Hardware watchpoint'
besides the correct one.
(Probably one for each shared lib loaded,
but I didn't check this).

  Andrew acknowledged that this was a separate problem in 
http://sources.redhat.com/ml/gdb-patches/2001-12/msg00178.html




Pierre Muller
Institut Charles Sadron
6,rue Boussingault
F 67083 STRASBOURG CEDEX (France)
mailto:muller@ics.u-strasbg.fr
Phone : (33)-3-88-41-40-07  Fax : (33)-3-88-41-40-99


  reply	other threads:[~2001-12-10 10:23 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-17 10:47 Pierre Muller
2001-11-28  9:44 ` Pierre Muller
2001-11-28 10:13 ` Eli Zaretskii
2001-11-17 16:07   ` Eli Zaretskii
2001-11-17 20:21   ` Christopher Faylor
2001-11-17 22:30     ` muller
2001-11-17 23:01       ` Christopher Faylor
2001-11-28 17:27         ` Christopher Faylor
2001-11-28 14:31       ` muller
2001-11-19  8:29     ` Eli Zaretskii
2001-11-21 15:15       ` Pierre Muller
2001-11-21 23:08         ` Christopher Faylor
2001-11-30  9:04           ` Christopher Faylor
2001-11-30  7:11         ` Pierre Muller
2001-11-29  0:12       ` Eli Zaretskii
2001-11-29  0:26       ` Pierre Muller
2001-11-19 11:30         ` Pierre Muller
2001-11-28 11:30     ` Christopher Faylor
2001-12-06  0:37     ` Pierre Muller
2001-12-06 13:30       ` Andrew Cagney
2001-12-07 16:59       ` Christopher Faylor
2001-12-10  2:23         ` Pierre Muller [this message]
2001-12-10 11:33           ` Christopher Faylor
2001-12-11  0:15             ` Eli Zaretskii
2001-12-11  1:04               ` Pierre Muller
2001-11-28 13:55   ` muller
2001-11-17 21:08     ` muller

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=4.2.0.58.20011210111416.013e24f0@ics.u-strasbg.fr \
    --to=muller@cerbere.u-strasbg.fr \
    --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