[gdbserver] win32, add OUTPUT_DEBUG_STRING_EVENT handling.

[Pedro Alves]

Pedro Alves wrote:
> Hi all,
>
> This patch adds support for sending OUTPUT_DEBUG_STRING_EVENT
> messages to the controller gdb.  Compared to the version found in
> gdb/win32-nat.c, this handles Unicode messages, needed for
> WinCE, but will not handle the special cygwin signal markers.
> Perhaps someone (maybe me) will get annoyed by the spurious console
> messages and implement proper support later.  I'm sending the messages
> using the 'O' packet, but somehow I guess that there should be an
> extra packet for these debugger-specific messages, and 'O' should be
> left for real output redirection, or would it be the other way
> around?  Anyway, the native debugger also puts the output debug
> strings into the console using warning, so...
>

In case I wasn't clear, this is needed so OutputDebugString 
messages/calls made
by the debuggee are seen on the controller gdb's console.

Here is an updated version.  It turns out Cygwin signals aren't 
handleable in gdb
yet, even in native debugging (I had assumed they where, based on what is
found in gdb/win32-nat.c, and ported the support to gdbserver, before I 
realized
they weren't), so, we might as well ignore the special Cygwin
OutputDebugStrings, like gdb/win32-nat.c.  Also, since we now have the new
monitor_output, I ditched my similar console_output.

OK?

Cheers,
Pedro Alves

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: outputdebugstring.diff
URL: <http://sourceware.org/pipermail/gdb-patches/attachments/20070228/1f904c2c/attachment.ksh>