Bug 33204 - [softpipe] firefox4 webgl: segfault in swrastPutImage
Summary: [softpipe] firefox4 webgl: segfault in swrastPutImage
Status: RESOLVED DUPLICATE of bug 33203
Alias: None
Product: Mesa
Classification: Unclassified
Component: Mesa core (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: mesa-dev
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-17 07:55 UTC by Sven Arvidsson
Modified: 2011-06-24 10:04 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
full backtrace (11.16 KB, text/plain)
2011-01-17 07:55 UTC, Sven Arvidsson
Details

Description Sven Arvidsson 2011-01-17 07:55:32 UTC
Created attachment 42121 [details]
full backtrace

Using git master 2bf52e7c28e6d48374c3c4314e06e3600d7f668a I get the following segfault when I try to run the WebGL conformance test:

Program received signal SIGSEGV, Segmentation fault.
swrastPutImage (draw=0xa9c26b00, op=3, x=0, y=0, w=621768704, h=-1249416532, 
    data=0x2c800000 "", loaderPrivate=0xa4ea6ac0) at drisw_glx.c:191
191	   ximage->width = w;

I'm not sure if it's the same as bug 33203 (the patch suggested there doesn't make a difference).

Firefox version is Minefield 4.0b10pre (2011-01-17)
Comment 1 Brian Paul 2011-01-17 09:22:35 UTC
Can you provide a stack trace at this point?  Some of those function parameters looks funny.
Comment 2 Sven Arvidsson 2011-01-17 10:26:19 UTC
(In reply to comment #1)
> Can you provide a stack trace at this point?  Some of those function parameters
> looks funny.

A backtrace is attached, or do I need to provide something else?
Comment 3 Karl Tomlinson 2011-01-17 16:59:15 UTC
Looks very similar to bug 33203.
Comment 4 Sven Arvidsson 2011-06-24 10:04:41 UTC
Let's mark this one as a duplicate. (Mostly because I can't figure out how to build softpipe nowadays)

*** This bug has been marked as a duplicate of bug 33203 ***


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.