Bug 23380 - glxChooseVisual: visualList might have not been initialized (crash)
Summary: glxChooseVisual: visualList might have not been initialized (crash)
Status: RESOLVED MOVED
Alias: None
Product: Mesa
Classification: Unclassified
Component: GLX (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: high critical
Assignee: mesa-dev
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-17 13:58 UTC by Stefano Maioli
Modified: 2019-09-18 17:11 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
fix (478 bytes, patch)
2009-08-17 13:58 UTC, Stefano Maioli 		Details | Splinter Review
Stack trace (3.82 KB, text/plain)
2009-08-17 13:59 UTC, Stefano Maioli 		Details
Possible fix (488 bytes, patch)
2009-08-22 17:52 UTC, Michel Dänzer 		Details | Splinter Review
Show Obsolete (1) View All

Description Stefano Maioli 2009-08-17 13:58:42 UTC 
Created attachment 28715 [details] [review]
fix

Bug introduced on 2009-05-12 07:34:13 by commit 	46b81b0cc883df0ef7d998be36ae6cbf80257cd2 .
Comment 1 Stefano Maioli 2009-08-17 13:59:30 UTC 
Created attachment 28716 [details]
Stack trace
Comment 2 Stefano Maioli 2009-08-17 16:18:03 UTC 
Update:
I've posted the patch in a hurry, and it doesn't appear to solve the problem. Sorry.

After some more careful debugging it seems that the crash happens the second time it loops, when visualList already holds a (valid?) pointer returned by XGetVisualInfo.

I'm available to provide more details if needed.
Comment 3 Michel Dänzer 2009-08-22 17:52:45 UTC 
Created attachment 28856 [details] [review]
Possible fix

Does this patch fix the problem?
Comment 4 GitLab Migration User 2019-09-18 17:11:18 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/56.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.