[Mono-bugs] [Bug 608558] New: mono --trace gives incomplete lines that should be logged, on Windows

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Tue May 25 04:55:37 EDT 2010



           Summary: mono --trace gives incomplete lines that should be
                    logged, on Windows
    Classification: Mono
           Product: Mono: Runtime
           Version: SVN
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: misc
        AssignedTo: mono-bugs at lists.ximian.com
        ReportedBy: aenomoto at novell.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---
           Blocker: ---

Run mono --trace=T:System.ServiceModel.Channels.TcpBinaryFrameManager on the
repro sample on bug #567672 . It somehow gives incomplete stack trace lines
e.g. it totally misses constructor call logs.

The head lines look like:

[00001808:] EXCEPTION handling: System.Configuration.ConfigurationException:
File 'C:\cygwin\home\atsushi\svn\olive\samples\wcf\tcp-transport\x.exe.config'
not found
Greetings service started
Client created
[00001808: 0
[00001A40: 0.44198 1] L
[000019C4: 0.50582 0] ENTER:
()(this:026FD440[System.ServiceModel.Channels.TcpBinaryFrameManager x.exe], )

Since WCF connection samples must be verified on three pairs of client/server
communication stack (.NET client / Mono service, Mono client / .NET serivice,
Mono client / Mono service), I have to debug this on Windows And --trace is
almost the only way to debug mono apps on Windows. 

So far I'M planning to dump away .NET interop and switch my development
environment to Linux.

Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.

More information about the mono-bugs mailing list