Re: syms_from_objfile() warnings and win32-nat.c IO redirection (Was: suppress annoying warnings about cygwin1.dbg)

Pedro Alves
2007-11-09T13:59:54Z

Christopher Faylor wrote:
>
> On Thu, Nov 08, 2007 at 11:48:41PM +0000, Pedro Alves wrote:
> > Pedro Alves wrote:
> >> Is there anything else preventing us from removing the
> >> stderr -> null redirection from win32-nat.c ?
> >
> > Like so ?
> >
> >2007-11-08 Pedro Alves <pedro_alves@portugalmail.pt>
> >
> > * win32-nat.c (safe_symbol_file_add_args,
> > safe_symbol_file_add_stub, safe_symbol_file_add_cleanup)
> > (safe_symbol_file_add): Remove.
> > (dll_symbol_command): Call symbol_file_add directly.
> >
>
> That would do it but removing that code would mean lots of console
> chatter unless you're debugging with the most recent, unreleased version
> of the DLL. I think we need to keep that code in gdb until the next version
> of cygwin is released - and that is not even on the horizon yet.
>

On the current Cygwin release, having cygwin1.dbg in
/usr/bin/cygwin1.dbg when the debug info is first loaded (normally, when
the inferior is ran), is already chatty on gdb head and unfortunatelly also
on 6.7.x (except for the new cygwin snapshots, of course) The redirection is
only done on the "dll-symbols" command. The warnings only happen on
cygwin1.dll. Every other dll should not have that problem, unless their
debug file format is also non conformant. I don't think that adding
cygwin1.dll manually is a common use case. If you don't want the
warnings on 6.7, we'll have to apply the cygwin1.dbg generation patch
on the 1.5 branch (, or wherever that is. A pretty safe patch, in my opinion).

Unless we're talking about a different set of warnings, in which
case, let's get those fixed.

Cheers,
Pedro Alves