<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8">
</head>
<body>
<div style="font-family:sans-serif"><div style="white-space:normal">
<p dir="auto">Well, if you are comfortable cutting that macro line out of your copy of ASDF, maybe you could tweak that line of code so that it prints the values of those variables?</p>

<p dir="auto">I'm wondering if this is a bug in SBCL instead of ASDF.  I can replicate your result: on SBCL, tracing <code style="background-color:#F7F7F7; border-radius:3px; margin:0; padding:0 0.4em" bgcolor="#F7F7F7">COMPILE-FILE</code> does not print anything.  <em>But</em> when I made this modification:<br><br>
<code style="background-color:#F7F7F7; border-radius:3px; margin:0; padding:0 0.4em" bgcolor="#F7F7F7"><br>
  (defun call-with-muffled-conditions (thunk conditions)<br>
    "calls the THUNK in a context where the CONDITIONS are muffled"<br>
    (handler-bind ((t #'(lambda (c) (when (match-any-condition-p c conditions)<br>
                                      (format t "~&MUFFLING CONDITION ~a~%" c)<br>
                                      (muffle-warning c)))))<br>
      (funcall thunk)))<br>
</code><br>
... then I <strong>did</strong> see output from tracing <code style="background-color:#F7F7F7; border-radius:3px; margin:0; padding:0 0.4em" bgcolor="#F7F7F7">COMPILE-FILE</code>.</p>

<p dir="auto">Also, on <em>neither</em> Allegro <em>nor</em> (my antique copy of) Clozure can I replicate this issue.</p>

<p dir="auto">Pending new evidence, I think this is for the SBCL folks to deal with...  Is there any chance that SBCL might have trouble tracing calls inside <code style="background-color:#F7F7F7; border-radius:3px; margin:0; padding:0 0.4em" bgcolor="#F7F7F7">APPLY</code>?  I can't see why this macro would make any difference, now that I see that it's not trying to muffle anything.</p>

<p dir="auto">Best,<br>
r</p>

<p dir="auto">On 9 Jun 2018, at 16:17, Cyrus Harmon wrote:</p>

</div>
<div style="white-space:normal"></div>
<blockquote style="border-left:2px solid #777; color:#777; margin:0 0 5px; padding-left:5px"><div id="A85CB580-C809-43AE-BD6F-BC5419D7D68C">
  <div text="#000000" bgcolor="#FFFFFF">
    <p>Ah, right.</p>
    <p>1. SBCL 1.4.8.53-eb16b4745 and ASDF 3.3.1</p>
    <p>2. I'm not sure if these change when running asdf:load-system,
      but for the moment they are all nil:<br>
    </p>
    <p>CL-USER> asdf::*uninteresting-conditions*<br>
      NIL<br>
      CL-USER> asdf::*uninteresting-compiler-conditions*<br>
      NIL<br>
      CL-USER> asdf::*warnings-file-type*<br>
      NIL<br>
    </p>
    <p>thanks,</p>
    <p>Cyrus<br>
    </p>
    <div class="moz-cite-prefix">On 6/9/18 2:13 PM, Robert Goldman
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:6C3BBA39-313D-4897-920F-F296FC372A69@sift.info">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <div style="font-family:sans-serif">
        <div style="white-space:normal">
          <p dir="auto">Two suggestions:</p>
          <ol>
            <li value="1">Let us know the implementation, implementation
              version, and ASDF version</li>
            <li value="2">Look at the values of <code
                style="background-color:#F7F7F7; border-radius:3px;
                margin:0; padding:0 0.4em" bgcolor="#F7F7F7">*uninteresting-conditions*</code>,
              <code style="background-color:#F7F7F7; border-radius:3px;
                margin:0; padding:0 0.4em" bgcolor="#F7F7F7">*uninteresting-compiler-conditions*</code>,
              and <code style="background-color:#F7F7F7;
                border-radius:3px; margin:0; padding:0 0.4em"
                bgcolor="#F7F7F7">*warnings-file-type*</code> in your
              running lisp.</li>
          </ol>
          <p dir="auto">That will help us figure out why you are seeing
            this effect.</p>
          <p dir="auto">Thanks,<br>
            r</p>
          <p dir="auto">On 9 Jun 2018, at 16:06, Cyrus Harmon wrote:</p>
        </div>
        <blockquote style="border-left:2px solid #777; color:#777;
          margin:0 0 5px; padding-left:5px">
          <div id="9D0074B1-2C16-47EA-BBDB-03BB73208779">
            <div text="#000000" bgcolor="#FFFFFF">
              <p>I don't know enough about ASDF to know if I'm running
                with deferred warnings -- I'm just trying to do
                (asdf:load-system ...) and removing the
                with-muffled-compiler-conditions form (which itself is
                inside a with-saved-deferred-warnings form) makes the
                trace output reappear. I could well be overestimating of
                that particular form, but somehow the TRACE output is
                being swallowed unless that form is removed.<br>
              </p>
              <div class="moz-cite-prefix">On 6/9/18 1:54 PM, Robert
                Goldman wrote:<br>
              </div>
              <blockquote type="cite"
                cite="mid:96FFDCC5-4722-4BF4-AD62-89C023F1BD5F@sift.info">
                <meta http-equiv="Content-Type" content="text/html;
                  charset=UTF-8">
                <div style="font-family:sans-serif">
                  <div style="white-space:normal">
                    <p dir="auto">On 9 Jun 2018, at 12:38, Cyrus Harmon
                      wrote:</p>
                    <blockquote style="border-left:2px solid #777;
                      color:#777; margin:0 0 5px; padding-left:5px">
                      <p dir="auto">Dear ASDF folks,</p>
                      <p dir="auto">I was trying to trace calls to
                        compile-file today and noticed that the
                        with-muffled-compiler-conditions form in
                        uiop:compile-file* muffles trace output. Is
                        there anyway to make it not do that?</p>
                      <p dir="auto">thanks,</p>
                      <p dir="auto">Cyrus</p>
                    </blockquote>
                    <p dir="auto">I think you are overestimating the
                      effect of this form. <strong>UNLESS</strong> you
                      are running with deferred warnings, this will only
                      muffle <code style="background-color:#F7F7F7;
                        border-radius:3px; margin:0; padding:0 0.4em"
                        bgcolor="#F7F7F7">*uninteresting-conditions*</code>
                      and <code style="background-color:#F7F7F7;
                        border-radius:3px; margin:0; padding:0 0.4em"
                        bgcolor="#F7F7F7">*uninteresting-compiler-conditions*</code>.</p>
                    <p dir="auto">By default, those are bound to <code
                        style="background-color:#F7F7F7;
                        border-radius:3px; margin:0; padding:0 0.4em"
                        bgcolor="#F7F7F7">NIL</code>, so this shouldn't
                      be causing your problem.</p>
                    <p dir="auto">R</p>
                  </div>
                </div>
              </blockquote>
            </div>
          </div>
        </blockquote>
        <div style="white-space:normal">
          <blockquote style="border-left:2px solid #777; color:#777;
            margin:0 0 5px; padding-left:5px">
          </blockquote>
        </div>
        <div style="white-space:normal">
        </div>
      </div>
    </blockquote>
  </div></div></blockquote>
<div style="white-space:normal">
<blockquote style="border-left:2px solid #777; color:#777; margin:0 0 5px; padding-left:5px">
</blockquote></div>
<div style="white-space:normal">
</div>
</div>
</body>
</html>