[CM] TRACE facility seems broken in 22.5

[David O'Toole]

Under what circumstances can the function "save-sound-as" produce this
output with no error message? The run simply stops, there's no error
message other than this:

save-sound-as: /tmp/snd_34010_7648.snd ()

On Tue, Jul 12, 2022 at 2:41 PM David O'Toole <deeteeoh1138 at gmail.com>
wrote:

> Never mind, I'm silly and missed the output. Thank you :)
>
> On Tue, Jul 12, 2022 at 2:39 PM David O'Toole <deeteeoh1138 at gmail.com>
> wrote:
>
>> Ok I tried the new trace in debug.scm and traced several functions, which
>> seems to succeed but then no trace is ever printed despite the functions
>> running.
>> The context was calling functions with a few arguments, formerly I could
>> trace any function I wanted.
>>
>> On Tue, Jul 12, 2022 at 2:32 PM <bil at ccrma.stanford.edu> wrote:
>>
>>> It seems to work for me (except for a function with just a
>>> rest arg, but that never worked).  What was the context?
>>> (I think this macro is found only in a couple test files --
>>> the new trace is in debug.scm).
>>>
>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://cm-mail.stanford.edu/pipermail/cmdist/attachments/20220712/f327cc5b/attachment-0001.html>