[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mesa3d-dev
Subject:    [Mesa3d-dev] [Bug 1730] __driUtilCreateScreen unitialized memory usage
From:       bugzilla-daemon () freedesktop ! org
Date:       2004-10-29 2:30:45
Message-ID: 20041029023045.4A53C9F473 () gabe ! freedesktop ! org
[Download RAW message or body]

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://freedesktop.org/bugzilla/show_bug.cgi?id=1730        
   




------- Additional Comments From idr@us.ibm.com  2004-10-28 19:30 -------
It appears that CallCreateNewScreen (src/glx/x11/glxext.c) has the same problem.
 That code does initialize framebuffer.dev_priv, but not the other two fields. 
I replaced the drmOpen call in that file with 'fd = -EPERM', and did *NOT* get a
crash.  I don't understand why GCC doesn't complain about variables being used
without being initialized.  Odd.        
   
   
--         
Configure bugmail: https://freedesktop.org/bugzilla/userprefs.cgi?tab=email       
   
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


-------------------------------------------------------
This Newsletter Sponsored by: Macrovision 
For reliable Linux application installations, use the industry's leading
setup authoring tool, InstallShield X. Learn more and evaluate 
today. http://clk.atdmt.com/MSI/go/ins0030000001msi/direct/01/
_______________________________________________
Mesa3d-dev mailing list
Mesa3d-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
[prev in list] [next in list] [prev in thread] [next in thread]