From: Pierre Muller <muller@ics.u-strasbg.fr>
To: gdb-patches@sources.redhat.com
Subject: [RFC/RFA] avoid spurious Watchpoint X output on cygwin native target.
Date: Mon, 15 Jul 2002 09:31:00 -0000 [thread overview]
Message-ID: <4.2.0.58.20020715174048.02a55688@ics.u-strasbg.fr> (raw)
The following patch suppresses all
spurious output when a DLL is loaded in native cygwin GDB.
Its a RFC for two reasons:
First reason:
Question: Why do we currently get ouptut while loading a DLL
while the safe_symbol_file_add does redefine gdb_stdout and
gdbstderr to dummy output exactly to suppress all output?
Answer: Because, despite gdb_stdout is redefined as a
dummy file does noting with the strings it gets
(and thus is a correct way of suppressing ouptut
sent to gdb_stdout), the Watchpoint X...
message is sent to uiout struct
(see mention function in breakpoint.c source)
The only question here is if a change of gdb_stdout should not
also change the global uiout variable behavior.
This could easily be achieved by replacing
the stream field of the data field of ui_out struct into a
'** ui_file' instead of a simple '*ui_file'.
Is that complete nonsense, or does it seem logical to someone?
(One argument for this is that you get the same unwanted output on
loading of shared libraries on linux for instance ...)
Here is the win32 specific patch and the associated changelog.
2nd reason: It does not free the uiout struct created because I didn't find
how to free this cleanly.
200-07-15 Pierre Muller <muller@ics.u-strasbg.fr>
* win32-nat.c: avoid unwanted ouptput about watchpoints on DLL loadings.
(struct safe_symbol_file_add_args): New field uiout to store
previous value of global uiout variable.
(safe_symbol_file_add_cleanup): restore uiout value.
(safe_symbol_file_add): store uiout and create a dummy one.
$ cvs diff -u -p win32-nat.c
Index: win32-nat.c
===================================================================
RCS file: /cvs/src/src/gdb/win32-nat.c,v
retrieving revision 1.60
diff -u -p -r1.60 win32-nat.c
--- win32-nat.c 11 Jul 2002 13:50:49 -0000 1.60
+++ win32-nat.c 15 Jul 2002 16:10:42 -0000
@@ -45,6 +45,9 @@
#include <imagehlp.h>
#include <sys/cygwin.h>
+
+#include "ui-out.h"
+#include "cli-out.h"
#include "buildsym.h"
#include "symfile.h"
#include "objfiles.h"
@@ -494,6 +497,7 @@ struct safe_symbol_file_add_args
int mainline;
int flags;
struct ui_file *err, *out;
+ struct ui_out *uiout;
struct objfile *ret;
};
@@ -534,6 +538,7 @@ safe_symbol_file_add_cleanup (void *p)
ui_file_delete (gdb_stdout);
gdb_stderr = sp->err;
gdb_stdout = sp->out;
+ uiout = sp->uiout;
#undef sp
}
@@ -550,10 +555,12 @@ safe_symbol_file_add (char *name, int fr
p.err = gdb_stderr;
p.out = gdb_stdout;
+ p.uiout = uiout;
gdb_flush (gdb_stderr);
gdb_flush (gdb_stdout);
gdb_stderr = ui_file_new ();
gdb_stdout = ui_file_new ();
+ uiout = cli_out_new (gdb_stdout);
p.name = name;
p.from_tty = from_tty;
p.addrs = addrs;
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 reply other threads:[~2002-07-15 16:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-15 9:31 Pierre Muller [this message]
2002-07-15 9:42 ` Daniel Jacobowitz
2002-07-16 7:24 ` Pierre 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.20020715174048.02a55688@ics.u-strasbg.fr \
--to=muller@ics.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