https://bugs.freedesktop.org/show_bug.cgi?id=33175
Jerome Glisse changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugs.freedesktop.org/show_bug.cgi?id=33175
Jerome Glisse changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugs.freedesktop.org/show_bug.cgi?id=33175
--- Comment #8 from revcompg...@gmail.com 2011-01-17 23:26:45 PST ---
So, I've been digging around with DDD in the crash, and I've found something
that looks pretty interesting to me. In _ae_ArrayElement(GLint) in
main/api_arrayelt.c the debugger
https://bugs.freedesktop.org/show_bug.cgi?id=33175
--- Comment #8 from revcompgeek at gmail.com 2011-01-17 23:26:45 PST ---
So, I've been digging around with DDD in the crash, and I've found something
that looks pretty interesting to me. In _ae_ArrayElement(GLint) in
main/api_arrayelt.c the debugg
https://bugs.freedesktop.org/show_bug.cgi?id=33175
--- Comment #7 from revcompg...@gmail.com 2011-01-17 21:36:19 PST ---
Okay, I finally figured out how to attach gdb to java, and after installing the
debug version of glibc and the latest mesa from git, I got this backtrace from
Minecraft:
(gdb)
https://bugs.freedesktop.org/show_bug.cgi?id=33175
--- Comment #7 from revcompgeek at gmail.com 2011-01-17 21:36:19 PST ---
Okay, I finally figured out how to attach gdb to java, and after installing the
debug version of glibc and the latest mesa from git, I got this backtrace from
Minecraft:
(gd
https://bugs.freedesktop.org/show_bug.cgi?id=33175
--- Comment #6 from revcompg...@gmail.com 2011-01-17 13:44:04 PST ---
Created an attachment (id=42136)
--> (https://bugs.freedesktop.org/attachment.cgi?id=42136)
glxinfo &> glxinfo.txt
--
Configure bugmail: https://bugs.freedesktop.org/userpref
https://bugs.freedesktop.org/show_bug.cgi?id=33175
--- Comment #6 from revcompgeek at gmail.com 2011-01-17 13:44:04 PST ---
Created an attachment (id=42136)
--> (https://bugs.freedesktop.org/attachment.cgi?id=42136)
glxinfo &> glxinfo.txt
--
Configure bugmail: https://bugs.freedesktop.org/userp
https://bugs.freedesktop.org/show_bug.cgi?id=33175
--- Comment #5 from revcompg...@gmail.com 2011-01-17 13:43:23 PST ---
(In reply to comment #4)
> (In reply to comment #3)
> > Classic. What's the difference? And how would I figure out what version?
> >
> glxinfo, unless you're running 32-bit Jav
https://bugs.freedesktop.org/show_bug.cgi?id=33175
--- Comment #5 from revcompgeek at gmail.com 2011-01-17 13:43:23 PST ---
(In reply to comment #4)
> (In reply to comment #3)
> > Classic. What's the difference? And how would I figure out what version?
> >
> glxinfo, unless you're running 32-bit
https://bugs.freedesktop.org/show_bug.cgi?id=33175
--- Comment #4 from Henri Verbeet 2011-01-17 12:11:42 PST
---
(In reply to comment #3)
> Classic. What's the difference? And how would I figure out what version?
>
glxinfo, unless you're running 32-bit Java on 64-bit Linux. You'll probably
want
https://bugs.freedesktop.org/show_bug.cgi?id=33175
--- Comment #4 from Henri Verbeet 2011-01-17 12:11:42
PST ---
(In reply to comment #3)
> Classic. What's the difference? And how would I figure out what version?
>
glxinfo, unless you're running 32-bit Java on 64-bit Linux. You'll probably
want
https://bugs.freedesktop.org/show_bug.cgi?id=33175
--- Comment #3 from revcompg...@gmail.com 2011-01-17 12:00:20 PST ---
(In reply to comment #2)
> I'm not sure if Java could cause it to look like that, but at first sight I'd
> say the driver is simply missing debug symbols. Also, is that classic
https://bugs.freedesktop.org/show_bug.cgi?id=33175
--- Comment #3 from revcompgeek at gmail.com 2011-01-17 12:00:20 PST ---
(In reply to comment #2)
> I'm not sure if Java could cause it to look like that, but at first sight I'd
> say the driver is simply missing debug symbols. Also, is that class
https://bugs.freedesktop.org/show_bug.cgi?id=33175
--- Comment #2 from Henri Verbeet 2011-01-17 03:58:57 PST
---
I'm not sure if Java could cause it to look like that, but at first sight I'd
say the driver is simply missing debug symbols. Also, is that classic r600 or
gallium, and which version?
https://bugs.freedesktop.org/show_bug.cgi?id=33175
--- Comment #2 from Henri Verbeet 2011-01-17 03:58:57
PST ---
I'm not sure if Java could cause it to look like that, but at first sight I'd
say the driver is simply missing debug symbols. Also, is that classic r600 or
gallium, and which version?
https://bugs.freedesktop.org/show_bug.cgi?id=33175
Michel Dänzer changed:
What|Removed |Added
Product|xorg|Mesa
Component|Driver/Radeon
https://bugs.freedesktop.org/show_bug.cgi?id=33175
Michel D?nzer changed:
What|Removed |Added
Product|xorg|Mesa
Component|Driver/Radeon
18 matches
Mail list logo
