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