[Bug 57] New: make sablevm messages go to stderr or a 3rd file descriptor

[email protected]
Newsgroups gmane.comp.java.vm.sablevm.bugs
Message-ID <[email protected]>
http://sablevm.org/bugs/show_bug.cgi?id=57

           Summary: make sablevm messages go to stderr or a 3rd file
                    descriptor
           Product: SableVM
           Version: unspecified
          Platform: All
               URL: http://thread.gmane.org/gmane.comp.java.vm.sablevm.devel
                    /865
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: default
        AssignedTo: [email protected]
        ReportedBy: [email protected]
         QAContact: [email protected]


This was discussed in March, and Greg and I just discussed it too.  stdout
should be reserved for Java application output, which means all sablevm messages
should go to stderr.  Additionally, in the event that the application itself
writes to stderr, you might want SableVM messages to go to a third file
descriptor, or as David suggested in the linked thread, perhaps just a file.

It is useful to separate the 2 (or 3) sources of output for benchmarking; I
already have all _svmf_printf()'s writing to stderr in my tree.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are the QA contact for the bug, or are watching the QA contact.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.