Posts

Post not yet marked as solved
3 Replies
0 Views
I've been having this problem every seed and have not found a fix. I just re-downloaded the beta access utility and re-ran that installer, as someone else mentioned it fixed it for them. But I won't know until next seed if it worked.
Post marked as solved
1 Replies
0 Views
Going to call this one resolved because I restarted and it solved itself... It could be that messaging in the console was just a side effect and the command line tool was authorized... But still disconcerting I can't actuall query it's authorization status?
Post not yet marked as solved
2 Replies
0 Views
Post marked as solved
6 Replies
0 Views
So I'm not sure what happened, but I came back this morning and everything is working great. The only big change was that Instruments was closed and re-opened since yesterday.
Post marked as solved
6 Replies
0 Views
Thanks! Unfortunetly they're tracing back to me. In list view I can tell that my start message is there, so they aren't coming from nowhere. But it seems like the end is not being captured. I'm setting up a signpost id per worker object/thead, and one of the functions being affected is a simple enough function that only has one exit point. Using the C API in case that matters.
Post marked as solved
6 Replies
0 Views
The other option I've thought of is that my app is highly multithreaded. I've started to move signpost stuff onto the main thread (ugh) just in case this is the issue, but it doesn't seem to be making things better, so I'm assuming that might not be it.