<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    To use this I would have to self-host mono, right? I'm currently
    just relying on the compiler to add the .NET build-up/tear-down.<br>
    <br>
    I was finally able to get VsPerfCollectionTools working for trace
    mode under wine, but not sampling mode. It required using vsinstr to
    instrument the binary, and I had to be careful about which functions
    I allowed to be instrumented. It seems if I let it instrument any
    .NET functions (with funcspecs like "my.nested.namespace.*" instead
    of "my::nested::namespace::*"), it would crash. But I was at least
    able to instrument C++ functions.<br>
    <br>
    Thanks for all the suggestions though everyone!<br>
    -Matt<br>
    <br>
    <br>
    <div class="moz-cite-prefix">On 7/1/2019 4:49 AM, Hin-Tak Leung
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:1055815702.1013001.1561970984850@mail.yahoo.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div> This is the relevant part of the documentation. So
        presumably you can do MONO_ENV_OPTIONS="--profile" and
        MONO_ENV_OPTIONS="--profile=stuff" , I believe.<br>
        <br>
        ===<br>
        <br>
        DEVELOPMENT OPTIONS<br>
        ...<br>
        --profile[=profiler[:profiler_args]]<br>
        Loads a profiler module with the given arguments. For more
        information, see the PROFILING section. This option can be used
        multiple times; each time will load an<br>
        additional profiler module.<br>
        <br>
        ENVIRONMENT VARIABLES<br>
        ...<br>
        MONO_ENV_OPTIONS<br>
        This environment variable allows you to pass command line
        arguments to a Mono process through the environment. This is
        useful for example to force all of your<br>
        Mono processes to use LLVM or SGEN without having to modify any
        launch scripts.<br>
        ===<br>
        <br>
      </div>
      <div class="yahoo_quoted" style="margin:10px 0px 0px
        0.8ex;border-left:1px solid #ccc;padding-left:1ex;">
        <div style="font-family:'Helvetica Neue', Helvetica, Arial,
          sans-serif;font-size:13px;color:#26282a;">
          <div> On Friday, 28 June 2019, 19:09:22 BST, Vincent Povirk
            <a class="moz-txt-link-rfc2396E" href="mailto:madewokdev@gmail.com"><madewokdev@gmail.com></a> wrote: </div>
          <div><br>
          </div>
          <div><br>
          </div>
          <div>
            <div id="yiv5459584568">
              <div>
                <div>
                  <div>The WINE_MONO_* variables are just the ones we've
                    added. Other MONO_* variables should generally work
                    the same as in regular Mono. I haven't worked with
                    Mono's profiling tools so I can't give any further
                    advice.<br clear="none">
                    <br clear="none">
                    <div class="yiv5459584568yqt5431541683"
                      id="yiv5459584568yqt57915">
                      <div class="yiv5459584568gmail_quote">
                        <div class="yiv5459584568gmail_attr" dir="ltr">On
                          Fri, Jun 28, 2019, 11:18 AM Hin-Tak Leung <<a
                            rel="nofollow" shape="rect"
                            ymailto="mailto:htl10@users.sourceforge.net"
                            target="_blank"
                            href="mailto:htl10@users.sourceforge.net"
                            moz-do-not-send="true">htl10@users.sourceforge.net</a>>
                          wrote:<br clear="none">
                        </div>
                        <blockquote class="yiv5459584568gmail_quote"
                          style="margin:0 0 0 .8ex;border-left:1px #ccc
                          solid;padding-left:1ex;">Hmm, I think
                          wine-mono has been working in 64-bit mode for
                          a while - although you have to invoke wine
                          explicitly as wine64 to hook into it . I think
                          there are some quirks about how wine and
                          wine-mono interacts, in such a way that you
                          cannot do 32-bit + 64-bit switches within the
                          process - i.e. you must do 64-bit wine to get
                          at 64-bit wine-mono. <br clear="none">
                          <br clear="none">
                          Do you notice any performance difference
                          between using wine-mono and dotnet472 64-bit ?<br
                            clear="none">
                          <br clear="none">
                          I am going back to wine-mono for your issue,
                          as mono supports setting profiling option via
                          environment variables (catering for exactly
                          this use case, when mono is running embedded
                          inside another process), and you can set
                          WINE_MONO_* variables to pass those along. I
                          am not sure about the exact details so you'll
                          need to look up the relevant docs, but I know
                          this is possible - mono has a built-in
                          profiler, and it is accessible and turned on
                          via environment variables.<br clear="none">
                          <br clear="none">
                          --------------------------------------------<br
                            clear="none">
                          On Tue, 25/6/19, Chambers, Matthew <<a
                            rel="nofollow" shape="rect"
                            ymailto="mailto:matt.chambers42@gmail.com"
                            target="_blank"
                            href="mailto:matt.chambers42@gmail.com"
                            moz-do-not-send="true">matt.chambers42@gmail.com</a>>
                          wrote:<br clear="none">
                          <br clear="none">
                           The application requires<br clear="none">
                           dotnet472 and 64-bit at that. I actually had
                          to add that<br clear="none">
                           verb to winetricks to get our application to
                          work. I'm<br clear="none">
                           definitely getting varying mileage! My<br
                            clear="none">
                           question is how to profile it with Windows
                          symbols so I can<br clear="none">
                           understand why and either help fix it in <br
                            clear="none">
                           Wine or possibly avoid the problem from my<br
                            clear="none">
                           application code.<br clear="none">
                          <br clear="none">
                          <br clear="none">
                          <br clear="none">
                        </blockquote>
                      </div>
                    </div>
                  </div>
                </div>
              </div>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>