In both cases, they are running on Intel machines.
Unfortunately these stack traces are from customers. I've never been able to reproduce this error on my own hardware, so I don't have full information on the context.
But, the stack traces below are the _full_ stack traces on those particular threads... which is strange since they're both thread 0 and my application stack is missing. I'm guessing that the llvm "interpreter" temporarily acts as its own "machine" and doesn't give stack trace information further back.
On Thu, Aug 28, 2008 at 2:29 AM, Paul Sargent <email@hidden> wrote:
On 28 Aug 2008, at 05:11, Chris Meyer wrote:
I'm getting strange crashes in my CoreImage/OpenGL application. The crashes have stack traces like this:
I've seen similar stack traces, and I think they're to do with when the OpenGL implementation falls back to software. It seems to use LLVM to generate code at run-time. This is especially true on the Intel graphics chips. At some point in the stack trace you should see your code, but it's normally 10-20 frames back.
What hardware are you on?
Do not post admin requests to the list. They will be ignored.
Quartz-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden