Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Valgrind errors in OpenGL.framework (mac) #147

Closed
burg opened this issue Oct 23, 2012 · 2 comments
Closed

Valgrind errors in OpenGL.framework (mac) #147

burg opened this issue Oct 23, 2012 · 2 comments
Labels

Comments

@burg
Copy link

@burg burg commented Oct 23, 2012

I don't know how to debug this, but it's pretty reliable (at least for me on OSX 10.7). It doesn't seem to result in any crashes, but that may be luck.

==12435== Thread 1:
==12435== Conditional jump or move depends on uninitialised value(s)
==12435==    at 0xCB69993: gldCreateVertexArray (in /System/Library/Extensions/ATIRadeonX3000GLDriver.bundle/Contents/MacOS/ATIRadeonX3000GLDriver)
==12435==    by 0xCB95C82: gldUpdateDispatch (in /System/Library/Extensions/ATIRadeonX3000GLDriver.bundle/Contents/MacOS/ATIRadeonX3000GLDriver)
==12435==    by 0xADEB14F: gleDoSelectiveDispatchCore (in /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLEngine.bundle/GLEngine)
==12435==    by 0xAD1C256: glClear_Exec (in /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLEngine.bundle/GLEngine)
==12435==    by 0xCC529D: __morestack (in /usr/local/lib/rustc/x86_64-apple-darwin/lib/librustrt.dylib)
==12435==    by 0x4072EFFFFFFFFFFF: ???
==12435==    by 0x101501E5F: ???
==12435==    by 0x1006BA82F: ???
==12435==    by 0xCB1618: rust_task::call_on_rust_stack(void*, void*) (in /usr/local/lib/rustc/x86_64-apple-darwin/lib/librustrt.dylib)
==12435==    by 0x1006BA82F: ???
==12435==    by 0xA2171F: display_callback::_1eb5d0efb52966e::_01 (in /Users/burg/repos/servo/build/src/rust-glut/libglut-94839cbfe144198-0.1.dylib)
==12435==    by 0x10159EFBF: ???
==12435== 
ChrisParis pushed a commit to ChrisParis/servo that referenced this issue Sep 7, 2014
Invalid values for the max and value attributes for the progress element
@DemiMarie
Copy link

@DemiMarie DemiMarie commented Oct 17, 2015

This looks like it related to split stacks, which Rust does not use anymore. Perhaps this should be closed?

@jdm
Copy link
Member

@jdm jdm commented Oct 18, 2015

Very plausible!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.