From: Andrew Cagney <ac131313@cygnus.com>
To: Pierre Muller <muller@cerbere.u-strasbg.fr>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC/RFA] Add hardware watchpoint support for cygwin target.
Date: Thu, 06 Dec 2001 13:30:00 -0000 [thread overview]
Message-ID: <3C0FE36E.2090803@cygnus.com> (raw)
In-Reply-To: <4.2.0.58.20011206092315.016150f0@ics.u-strasbg.fr>
> The last problem is the unwanted gdb output, but here again,
> this is NOT a cygwin specific bug, as it is also present for linux target.
> Each time a DLL (cygwin target) or a shared lib (linux target) is
> loaded, all breakpoints are re-setted, and the mention function does
> generate an output even if the output have been disabled by gdb_stdout and gdb_stderr.
> 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.
A note on ui-out. Typically stray output problem come from code that
still uses printf(). Sorting that out is a separate problem.
enjoy,
Andrew
next prev parent reply other threads:[~2001-12-06 21:30 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 [this message]
2001-12-07 16:59 ` Christopher Faylor
2001-12-10 2:23 ` Pierre Muller
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=3C0FE36E.2090803@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=muller@cerbere.u-strasbg.fr \
/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