Status: New Owner: ---- New issue 255 by sgbeal: --trace-gc engine argument should trace to stderr, not stdout http://code.google.com/p/v8/issues/detail?id=255
i'm working on ncurses bindings for v8 and i've found that it's impossible to use --trace-gc because that trigger sends output to stdout instead of stderr (which hoses the curses screen that). i can redirect stderr with: step...@jareth:~/cvs/fossil/v8-addons/addons$ ./shell --trace-gc js/nc-test.js 2>/dev/pts/1 but ncurses requires stdout for its own use, which means i can't use --trace-gc with it. This isn't just a problem for curses, but also for apps which generate formatted output (XML, SQL, etc) to stdout. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev -~----------~----~----~----~------~----~------~--~---
