From: Pierre Muller <muller@cerbere.u-strasbg.fr>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches <gdb-patches@sources.redhat.com>
Subject: Re: [RFC/RFA] Add hardware watchpoint support for cygwin target.
Date: Wed, 21 Nov 2001 15:15:00 -0000 [thread overview]
Message-ID: <4.2.0.58.20011130160404.00aca750@ics.u-strasbg.fr> (raw)
In-Reply-To: <Pine.SUN.3.91.1011129101134.10998E-100000@is>
At 09:12 29/11/2001 , vous avez écrit:
>On Wed, 28 Nov 2001, Christopher Faylor wrote:
>
> > It seems like the described behavior would be annoying indeed. It
> > would be nice to fix this.
>
>I second that.
More info:
The unwanted output comes from an ui_out_text call
inside mention when a new DLL is loaded
After some debugging, I think that the problem
arrises at some hidden stops (causes by events like DLL loading)
that do call to new_symfile_objfile,
that does call breakpoint_re_set
that finally calls breakpoint_re_set_one for each enabled
break or watch point.
What is strange is that this new_symfile_objfile call
is encapsulated in safe_symbol_file_add
that does temporarily disable all output by
change gdb_stdout and gdb_stderr into
dummy versions.
I suspect that the problem comes from the fact that uiout
still remains associated to the normal gdb_stdout.
This is the only way I can understand why most messages are suppressed
but not these.
I am completely uncompetent in the UI area,
so someone else can probably better confirm or infirm
my deductions.
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
WARNING: multiple messages have this Message-ID
From: Pierre Muller <muller@cerbere.u-strasbg.fr>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches <gdb-patches@sources.redhat.com>
Subject: Re: [RFC/RFA] Add hardware watchpoint support for cygwin target.
Date: Fri, 30 Nov 2001 07:11:00 -0000 [thread overview]
Message-ID: <4.2.0.58.20011130160404.00aca750@ics.u-strasbg.fr> (raw)
Message-ID: <20011130071100.fNwgKR0k4DpgdvH9JOf_aRKjRCzvToNFumkvdH3firU@z> (raw)
In-Reply-To: <Pine.SUN.3.91.1011129101134.10998E-100000@is>
At 09:12 29/11/2001 , vous avez écrit:
>On Wed, 28 Nov 2001, Christopher Faylor wrote:
>
> > It seems like the described behavior would be annoying indeed. It
> > would be nice to fix this.
>
>I second that.
More info:
The unwanted output comes from an ui_out_text call
inside mention when a new DLL is loaded
After some debugging, I think that the problem
arrises at some hidden stops (causes by events like DLL loading)
that do call to new_symfile_objfile,
that does call breakpoint_re_set
that finally calls breakpoint_re_set_one for each enabled
break or watch point.
What is strange is that this new_symfile_objfile call
is encapsulated in safe_symbol_file_add
that does temporarily disable all output by
change gdb_stdout and gdb_stderr into
dummy versions.
I suspect that the problem comes from the fact that uiout
still remains associated to the normal gdb_stdout.
This is the only way I can understand why most messages are suppressed
but not these.
I am completely uncompetent in the UI area,
so someone else can probably better confirm or infirm
my deductions.
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
next prev parent reply other threads:[~2001-11-30 15:11 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 [this message]
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
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.20011130160404.00aca750@ics.u-strasbg.fr \
--to=muller@cerbere.u-strasbg.fr \
--cc=eliz@is.elta.co.il \
--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