Hi,
Personaly, I'm logging to /Library/Preferences/Audio/mylogfile.
This is one of the few area you have access to from the sandboxed
coreaudiod.

About the breakpoints, I followed this
https://groups.google.com/d/msg/coreaudio-api/PDQ3V5NrGI0/RvsgjFHqqcwJ
and it worked (I did not try since I upgraded to 10.10 and the latest
xcode, so make a prayer)

Fred


2015-04-24 2:04 GMT+02:00 Seth Willits <[email protected]>:

> Two things:
>
>
>
> 1) I can manage to get the debugger to attach to coreaudiod, but it never
> stops on any breakpoints.
>
> I've read the past mailing list threads on debugging, for example
> https://groups.google.com/d/msg/coreaudio-api/g5TrSW4hJFw/W6S8SZu7NE0J
>
> The debugger attaches as root when coreaudiod fires up, and I can pause
> the debugger and see the threads etc, but it never breaks on the
> breakpoints I have set in any of the functions in the AudioServerPlugIn
> which I know are being called. For example NullAudio_Create and
> NullAudio_QueryInterface in the Apple sample project.
>
>
>
> 2) I can't get any messages to show up in the system log. I've tried
> syslog and asl_log_message at variously increasingly critical log levels,
> and none of the messages show up in Console despite knowing that these
> functions are getting called.
>
>
>
> Between the two of these problems, I can't even begin to debug anything.
> Suggestions?
>
>
>
> --
> Seth Willits
>
>
>
>
>  _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Coreaudio-api mailing list      ([email protected])
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/coreaudio-api/fastphilg%40gmail.com
>
> This email sent to [email protected]
 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/coreaudio-api/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to