From derek.br...@gmail.com on April 19, 2010 09:17:00

the issues with drinject are easily fixed: improper handle setup when creating the
child process. that's issue #142 /PR 208715.

this issue is different: DR's NtWriteFile to the stdout/stderr handles does not show
up in the cmd window. this is because WriteFile to a console handle calls
WriteConsole and never gets to NtWriteFile: instead it calls CsrClientCallServer and
csrss handle the write. so DR and clients can't easily write to the cmd console.

Summary: [windows] DR print to stdout/stderr does not show up in cmd

From derek.br...@gmail.com on May 26, 2010 20:36:04

in r344 :
drsysm, which is already loading a private kernel32,
now exports drsym_write_to_console().

• Not bothering to support stdout: only stderr.
• Supports printing to both cmd and other windows.
  Unfortunately there are significant limitations to this console
  printing support:
• It does not work from the exit event. Once the application terminates
  its state with csrss (toward the very end of ExitProcess), no output
  will show up on the console. We have no good solution here yet as exiting
  early is not ideal.
• It does not work at all from graphical applications, even when they are
  launched from a console.
• In the future, with earliest injection ( issue Windows earliest injection #234 ), writing to the
  console may not work from the client init event.

From bruen...@google.com on February 22, 2013 19:09:09

even with dr_enable_console_printing(), there's not output in cmd on win2k.
this shows up in Dr. Memory where -results_to_stderr is all blank.
redirecting stderr to a file shows it all.

From bruen...@google.com on February 24, 2013 22:08:42

scratch the win2k comment: that was actually issue #1089