Please do not reply to this email: if you want to comment on the bug, go to
the URL shown below and enter yourcomments there.
https://bugs.freedesktop.org/show_bug.cgi?id=7371
------- Additional Comments From [EMAIL PROTECTED] 2006-07-01 13:47 -------
Erm,
Yes using valgrind is very entertaining, it ends with this:
==3017== More than 10000000 total errors detected. I'm not reporting any more.
==3017== Final error counts will be inaccurate. Go fix your program!
==3017== Rerun with --error-limit=no to disable this cutoff. Note
==3017== that errors may occur in your program without prior warning from
==3017== Valgrind, because errors are no longer being displayed.
I did take a somewhat closer look, but I'm not famliar enough with the r300 code
(or with mesa / X at all) to get very far I noticed these 3 warnings many times:
==3017== Conditional jump or move depends on uninitialised value(s)
==3017== at 0x965FBA2: r300GartOffsetFromVirtual (r300_ioctl.c:902)
==3017== by 0x96796D3: emit_vector (r300_maos.c:201)
==3017== by 0x9679E41: r300EmitArrays (r300_maos.c:339)
==3017== by 0x966B782: r300_run_vb_render (r300_render.c:386)
==3017== by 0x966C360: r300_run_tcl_render (r300_render.c:575)
==3017== by 0x9738273: _tnl_run_pipeline (t_pipeline.c:162)
==3017== by 0x977A346: _tnl_flush_vtx (t_vtx_exec.c:281)
==3017== by 0x9773D1C: _tnl_FlushVertices (t_vtx_api.c:873)
==3017== by 0x96D2866: _mesa_PopMatrix (matrix.c:270)
==3017== by 0x40B60C: (within /usr/bin/ppracer)
==3017== by 0x454C22: (within /usr/bin/ppracer)
==3017== by 0x45F65A: (within /usr/bin/ppracer)
==3017== Use of uninitialised value of size 8
==3017== at 0x96792B8: emit_vec8 (r300_maos.c:116)
==3017== by 0x967974E: emit_vector (r300_maos.c:213)
==3017== by 0x9679E41: r300EmitArrays (r300_maos.c:339)
==3017== by 0x966B782: r300_run_vb_render (r300_render.c:386)
==3017== by 0x966C360: r300_run_tcl_render (r300_render.c:575)
==3017== by 0x9738273: _tnl_run_pipeline (t_pipeline.c:162)
==3017== by 0x977A346: _tnl_flush_vtx (t_vtx_exec.c:281)
==3017== by 0x9773D1C: _tnl_FlushVertices (t_vtx_api.c:873)
==3017== by 0x96D2866: _mesa_PopMatrix (matrix.c:270)
==3017== by 0x40B60C: (within /usr/bin/ppracer)
==3017== by 0x454C22: (within /usr/bin/ppracer)
==3017== by 0x45F65A: (within /usr/bin/ppracer)
==3017== Conditional jump or move depends on uninitialised value(s)
==3017== at 0x965FB0E: r300IsGartMemory (r300_ioctl.c:886)
==3017== by 0x9679821: r300EmitElts (r300_maos.c:237)
==3017== by 0x966AEEC: r300_render_vb_primitive (r300_render.c:311)
==3017== by 0x966B98F: r300_run_vb_render (r300_render.c:437)
==3017== by 0x965A944: radeonDrawElements (radeon_vtxfmt_a.c:335)
==3017== by 0x9727C29: neutral_DrawElements (vtxfmt_tmp.h:341)
==3017== by 0x4479C0: (within /usr/bin/ppracer)
==3017== by 0x44BF9D: (within /usr/bin/ppracer)
==3017== by 0x41DF33: (within /usr/bin/ppracer)
==3017== by 0x41F033: (within /usr/bin/ppracer)
==3017== by 0x434DB4: (within /usr/bin/ppracer)
==3017== by 0x45F65A: (within /usr/bin/ppracer)
I think that the emit_vec8 case _may_ be caused by the r300IsGartMemory case as
emit_vec8 calls r300IsGartMemory and acts on the result when this waring is
caused.
The other 2 both seem to indicate that
rmesa->radeon.radeonScreen->gartTextures.size is uninitialised.
I've set a breakpoint in gdb on r300GartOffsetFromVirtual, and then printed the
contents of l jump or move depends on uninitialised value(s)
==3017== at 0x965FBA2: r300GartOffsetFromVirtual (r300_ioctl.c:902)
==3017== by 0x96796D3: emit_vector (r300_maos.c:201)
==3017== by 0x9679E41: r300EmitArrays (r300_maos.c:339)
==3017== by 0x966B782: r300_run_vb_render (r300_render.c:386)
==3017== by 0x966C360: r300_run_tcl_render (r300_render.c:575)
==3017== by 0x9738273: _tnl_run_pipeline (t_pipeline.c:162)
==3017== by 0x977A346: _tnl_flush_vtx (t_vtx_exec.c:281)
==3017== by 0x9773D1C: _tnl_FlushVertices (t_vtx_api.c:873)
==3017== by 0x96D2866: _mesa_PopMatrix (matrix.c:270)
==3017== by 0x40B60C: (within /usr/bin/ppracer)
==3017== by 0x454C22: (within /usr/bin/ppracer)
==3017== by 0x45F65A: (within /usr/bin/ppracer)
==3017== Use of uninitialised value of size 8
==3017== at 0x96792B8: emit_vec8 (r300_maos.c:116)
==3017== by 0x967974E: emit_vector (r300_maos.c:213)
==3017== by 0x9679E41: r300EmitArrays (r300_maos.c:339)
==3017== by 0x966B782: r300_run_vb_render (r300_render.c:386)
==3017== by 0x966C360: r300_run_tcl_render (r300_render.c:575)
==3017== by 0x9738273: _tnl_run_pipeline (t_pipeline.c:162)
==3017== by 0x977A346: _tnl_flush_vtx (t_vtx_exec.c:281)
==3017== by 0x9773D1C: _tnl_FlushVertices (t_vtx_api.c:873)
==3017== by 0x96D2866: _mesa_PopMatrix (matrix.c:270)
==3017== by 0x40B60C: (within /usr/bin/ppracer)
==3017== by 0x454C22: (within /usr/bin/ppracer)
==3017== by 0x45F65A: (within /usr/bin/ppracer)
==3017== Conditional jump or move depends on uninitialised value(s)
==3017== at 0x965FB0E: r300IsGartMemory (r300_ioctl.c:886)
==3017== by 0x9679821: r300EmitElts (r300_maos.c:237)
==3017== by 0x966AEEC: r300_render_vb_primitive (r300_render.c:311)
==3017== by 0x966B98F: r300_run_vb_render (r300_render.c:437)
==3017== by 0x965A944: radeonDrawElements (radeon_vtxfmt_a.c:335)
==3017== by 0x9727C29: neutral_DrawElements (vtxfmt_tmp.h:341)
==3017== by 0x4479C0: (within /usr/bin/ppracer)
==3017== by 0x44BF9D: (within /usr/bin/ppracer)
==3017== by 0x41DF33: (within /usr/bin/ppracer)
==3017== by 0x41F033: (within /usr/bin/ppracer)
==3017== by 0x434DB4: (within /usr/bin/ppracer)
==3017== by 0x45F65A: (within /usr/bin/ppracer)
I think that the emit_vec8 case _may_ be caused by the r300IsGartMemory case as
emit_vec8 calls r300IsGartMemory and acts on the result when this waring is
caused.
The other 2 both seem to indicate that
rmesa->radeon.radeonScreen->gartTextures.size is uninitialised.
I've set a breakpoint in gdb on r300GartOffsetFromVirtual, and then printed the
contents of l jump or move depends on uninitialised value(s)
==3017== at 0x965FBA2: r300GartOffsetFromVirtual (r300_ioctl.c:902)
==3017== by 0x96796D3: emit_vector (r300_maos.c:201)
==3017== by 0x9679E41: r300EmitArrays (r300_maos.c:339)
==3017== by 0x966B782: r300_run_vb_render (r300_render.c:386)
==3017== by 0x966C360: r300_run_tcl_render (r300_render.c:575)
==3017== by 0x9738273: _tnl_run_pipeline (t_pipeline.c:162)
==3017== by 0x977A346: _tnl_flush_vtx (t_vtx_exec.c:281)
==3017== by 0x9773D1C: _tnl_FlushVertices (t_vtx_api.c:873)
==3017== by 0x96D2866: _mesa_PopMatrix (matrix.c:270)
==3017== by 0x40B60C: (within /usr/bin/ppracer)
==3017== by 0x454C22: (within /usr/bin/ppracer)
==3017== by 0x45F65A: (within /usr/bin/ppracer)
==3017== Use of uninitialised value of size 8
==3017== at 0x96792B8: emit_vec8 (r300_maos.c:116)
==3017== by 0x967974E: emit_vector (r300_maos.c:213)
==3017== by 0x9679E41: r300EmitArrays (r300_maos.c:339)
==3017== by 0x966B782: r300_run_vb_render (r300_render.c:386)
==3017== by 0x966C360: r300_run_tcl_render (r300_render.c:575)
==3017== by 0x9738273: _tnl_run_pipeline (t_pipeline.c:162)
==3017== by 0x977A346: _tnl_flush_vtx (t_vtx_exec.c:281)
==3017== by 0x9773D1C: _tnl_FlushVertices (t_vtx_api.c:873)
==3017== by 0x96D2866: _mesa_PopMatrix (matrix.c:270)
==3017== by 0x40B60C: (within /usr/bin/ppracer)
==3017== by 0x454C22: (within /usr/bin/ppracer)
==3017== by 0x45F65A: (within /usr/bin/ppracer)
==3017== Conditional jump or move depends on uninitialised value(s)
==3017== at 0x965FB0E: r300IsGartMemory (r300_ioctl.c:886)
==3017== by 0x9679821: r300EmitElts (r300_maos.c:237)
==3017== by 0x966AEEC: r300_render_vb_primitive (r300_render.c:311)
==3017== by 0x966B98F: r300_run_vb_render (r300_render.c:437)
==3017== by 0x965A944: radeonDrawElements (radeon_vtxfmt_a.c:335)
==3017== by 0x9727C29: neutral_DrawElements (vtxfmt_tmp.h:341)
==3017== by 0x4479C0: (within /usr/bin/ppracer)
==3017== by 0x44BF9D: (within /usr/bin/ppracer)
==3017== by 0x41DF33: (within /usr/bin/ppracer)
==3017== by 0x41F033: (within /usr/bin/ppracer)
==3017== by 0x434DB4: (within /usr/bin/ppracer)
==3017== by 0x45F65A: (within /usr/bin/ppracer)
I think that the emit_vec8 case _may_ be caused by the r300IsGartMemory case as
emit_vec8 calls r300IsGartMemory and acts on the result when this waring is
caused.
The other 2 both seem to indicate that
rmesa->radeon.radeonScreen->gartTextures.size is uninitialised.
I've set a breakpoint in gdb on r300GartOffsetFromVirtual, and then printed the
contents of rmesa->radeon.radeonScreen->gartTextures. I'm not supposed how
things are supposed to look, but this inded seems odd:
{handle = 3492814848, size = 5111808, map = 0x2aaab7233000}
Anyways I've spent way too much time on this r300 experiment as is already,
without any real progress. So i'm dropping my good old 9250 back in my PC for
know (thats much quiter too!).
Let me know if there is anything else I can do. I do believe that valgrind can
be a helpfull tool for debugging this, but it needs to be in the hands of
someone more familiar with the code.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
