[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

Nicolai Hähnle  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|NEW |RESOLVED

--- Comment #71 from Nicolai Hähnle  ---
commit 98c348d26b28a662d093543ecb7ca839e7883e8e

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

--- Comment #70 from bellamort...@gmail.com ---
Understood.  Thank you for putting in the extra work to make this happen, it's
much appreciated.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

--- Comment #69 from Nicolai Hähnle  ---
bellamorte, feel free to bring this issue to the attention of the gcc and Clang
people. It's kind of borderline between a bug and a misfeature.

The ::visit method was really huge and got a lot of functions inlined, and it's
possible that gcc could do a better job at aliasing the additional stack
variables, though I didn't bother to investigate in detail.

For Mesa, the pragmatic thing is clearly to just work around it :)

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

--- Comment #68 from Felix Schwarz  ---
(In reply to higuita from comment #67)
> May i suggest to include this patch in any maintenance/bugfix release for
> mesa 11.x?

in linked patch (see patchwork link above) you'll find:
Cc: "11.1 11.2" 

This means the Mesa release manager should pick up the patch automatically for
all stable releases of mesa 11.1 and 11.2.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

--- Comment #67 from higu...@gmx.net ---
May i suggest to include this patch in any maintenance/bugfix release for mesa
11.x? this would help pushing this to distros updates and to normal linux users
and not have to wait 6+ months for the workaround

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

--- Comment #66 from bellamort...@gmail.com ---
Let me get this straight, they refused to fix the optimization bug so you were
forced to work around it?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

--- Comment #65 from Nicolai Hähnle  ---
Probably nothing :)

This patch will likely fix the problem:
https://patchwork.freedesktop.org/patch/83779/

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

--- Comment #64 from higu...@gmx.net ---
So what a non-programmer user can do to help having this fixed?

I have recompiled mesa to workaround this, but many other people have this
problem and can't/don't know recompile mesa.

I can ask Gaijin for a way to disable the "freeze detect", it that helps (as it
blocks valgrind from reaching the crash point)

What help i can help?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

--- Comment #63 from Michel Dänzer  ---
(In reply to Iaroslav Andrusyak from comment #61)
> Works for me with aces -safe and with any settings but without shadows
> enabled, with shadows i got 
> 
> state_tracker/st_cb_fbo.c:431:st_update_renderbuffer_surface: Assertion
> `level <= resource->last_level' failed.

Please file a new report about that, since it's a different bug from the one
this report is about.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

--- Comment #62 from Nicolai Hähnle  ---
Hi Iaroslav, do you have an apitrace with shadows enabled that triggers the
assertion?

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

--- Comment #61 from Iaroslav Andrusyak  ---
hd 7790 mesa-git
Works for me with aces -safe and with any settings but without shadows enabled,
with shadows i got 

state_tracker/st_cb_fbo.c:431:st_update_renderbuffer_surface: Assertion `level
<= resource->last_level' failed.


standart suse cflags gcc 4.8
-fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2
-fstack-protector -funwind-tables -fasynchronous-unwind-tables -g -DNDEBUG

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

higu...@gmx.net changed:

   What|Removed |Added

 CC||higu...@gmx.net

-- 
You are receiving this mail because:
You are the assignee for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

--- Comment #60 from higu...@gmx.net ---
Created attachment 122976
  --> https://bugs.freedesktop.org/attachment.cgi?id=122976=edit
apitrace using radeon

Using ubuntu 15.10 with oibaf PPA, we get the crash using the intel and the
radeon drivers. But i found that with intel we can start the game with "./aces
-safe", where in radeon, with or without it, it still crashes

Attach is the apitrace for the radeon. I don't see different warnings for the
intel one, but i can upload it also

i notice that the apitrace reports this:

- 0:1(10): error: GLSL 1.50 is not supported. Supported versions are: 1.10,
1.20, 1.30, 1.00 ES, and 3.00 ES

Did mesa forgot to announce 1.50?

and the final error is
- High severity API error 18, GL_INVALID_OPERATION in glMapBufferRange(buffer
does not allow write access)

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

--- Comment #59 from har...@gmx.de ---
... sorry, i have to admit:

My last comment is incorrect, there is still a crash with latest mesa git
and latest War-Thunder client.

(i was testing earlier builds in different directory, without being aware of
this)

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

--- Comment #58 from har...@gmx.de ---
This bug seems no longer present.

Building latest mesa from git with default settings (-O2),
result in a driver working flawless with latest War-Thunder now.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

Konstantin A. Lepikhov  changed:

   What|Removed |Added

 CC||lakos...@altlinux.org

-- 
You are receiving this mail because:
You are the assignee for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

--- Comment #57 from Ernst Sjöstrand  ---
With current git I get a crash like this:

0x726ff349 in glsl_to_tgsi_visitor::visit (this=0x7fffa2725600,
ir=0x7fffa271baf8) at state_tracker/st_glsl_to_tgsi.cpp:3161
3161   const glsl_type *sampler_type = ir->sampler->type;


(gdb) bt full
#0  0x726ff349 in glsl_to_tgsi_visitor::visit (this=0x7fffa2725600,
ir=0x7fffa271baf8) at state_tracker/st_glsl_to_tgsi.cpp:3161
result_src = {file = PROGRAM_UNDEFINED, index = 0, index2D = 0, swizzle
= 0, negate = 0, type = 13, reladdr = 0x0, reladdr2 = ,
has_index2 = , 
  double_reg2 = , array_id = ,
is_double_vertex_input = }
coord = {file = PROGRAM_UNDEFINED, index = 0, index2D = 0, swizzle = 0,
negate = 0, type = 13, reladdr = 0x0, reladdr2 = , has_index2 =
, 
  double_reg2 = , array_id = ,
is_double_vertex_input = }
cube_sc = {file = PROGRAM_UNDEFINED, index = 0, index2D = 0, swizzle =
0, negate = 0, type = 13, reladdr = 0x0, reladdr2 = , has_index2
= , 
  double_reg2 = , array_id = ,
is_double_vertex_input = }
lod_info = {file = PROGRAM_UNDEFINED, index = 0, index2D = 0, swizzle =
0, negate = 0, type = 13, reladdr = 0x0, reladdr2 = , has_index2
= , 
  double_reg2 = , array_id = ,
is_double_vertex_input = }
projector = {file = PROGRAM_UNDEFINED, index = 0, index2D = 0, swizzle
= 0, negate = 0, type = 13, reladdr = 0x0, reladdr2 = ,
has_index2 = , 
  double_reg2 = , array_id = ,
is_double_vertex_input = }
dx = {file = PROGRAM_UNDEFINED, index = 0, index2D = 0, swizzle = 0,
negate = 0, type = 13, reladdr = 0x0, reladdr2 = , has_index2 =
, 
  double_reg2 = , array_id = ,
is_double_vertex_input = }
dy = {file = PROGRAM_UNDEFINED, index = 0, index2D = 0, swizzle = 0,
negate = 0, type = 13, reladdr = 0x0, reladdr2 = , has_index2 =
, 
  double_reg2 = , array_id = ,
is_double_vertex_input = }
offset = {{file = PROGRAM_UNDEFINED, index = 0, index2D = 0, swizzle =
0, negate = 0, type = 13, reladdr = 0x0, reladdr2 = 0x0, has_index2 = false,
double_reg2 = false, 
array_id = 0, is_double_vertex_input = false}, {file =
PROGRAM_UNDEFINED, index = 0, index2D = 0, swizzle = 0, negate = 0, type = 13,
reladdr = 0x0, reladdr2 = 0x0, 
has_index2 = false, double_reg2 = false, array_id = 0,
is_double_vertex_input = false}, {file = PROGRAM_UNDEFINED, index = 0, index2D
= 0, swizzle = 0, negate = 0, 
type = 13, reladdr = 0x0, reladdr2 = 0x0, has_index2 = false,
double_reg2 = false, array_id = 0, is_double_vertex_input = false}, {file =
4067491840, index = 0, 
index2D = 0, swizzle = 89, negate = 12, type = 6, reladdr =
0x4000, reladdr2 = 0x0, has_index2 = false, double_reg2 = false, array_id =
0, 
is_double_vertex_input = false}}
sample_index = 
component = 
levels_src = 
result_dst = 
coord_dst = 
cube_sc_dst = 
inst = 
opcode = 
sampler_type = 
sampler_index = 
is_cube_array = 
i = 


(gdb) p *(ir->sampler)
$8 = { = { = { = {next = 0x0, prev =
0x0}, _vptr.ir_instruction = 0x72e23b90 , 
  ir_type = ir_type_dereference_variable}, type = 0x72e3fcc0
}, }

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

--- Comment #56 from bellamort...@gmail.com ---
Still occurs with latest mesa git and llvm.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

--- Comment #54 from Jose Fonseca  ---
(In reply to Nicolai Hähnle from comment #53)
> The 'FBO incomplete' message is something that is often seen with apitrace.
> Not sure where it actually comes from, but in other cases it doesn't cause
> problems.

Here's the stack back trace:

#0  glretrace::debugOutputCallback (source=33350, type=33361, id=1,
severity=37191, length=36, message=0x7fffc2c0 "FBO incomplete: no
attachments [-1]\n", userParam=0xb32a60)
at retrace/glretrace_main.cpp:472
#1  0x743ec3f6 in log_msg_locked_and_unlock (ctx=0x77fd1010,
source=MESA_DEBUG_SOURCE_API, type=MESA_DEBUG_TYPE_OTHER, id=1,
severity=MESA_DEBUG_SEVERITY_MEDIUM, 
len=36, buf=0x7fffc2c0 "FBO incomplete: no attachments [-1]\n") at
src/mesa/main/errors.c:865
#2  0x743ec49b in log_msg (ctx=0x77fd1010,
source=MESA_DEBUG_SOURCE_API, type=MESA_DEBUG_TYPE_OTHER, id=1,
severity=MESA_DEBUG_SEVERITY_MEDIUM, len=36, 
buf=0x7fffc2c0 "FBO incomplete: no attachments [-1]\n") at
src/mesa/main/errors.c:886
#3  0x743ed656 in _mesa_gl_vdebug (ctx=0x77fd1010,
id=0x75b1e050 , source=MESA_DEBUG_SOURCE_API,
type=MESA_DEBUG_TYPE_OTHER, 
severity=MESA_DEBUG_SEVERITY_MEDIUM, fmtString=0x752e743d "FBO
incomplete: %s [%d]\n", args=0x7fffd320) at src/mesa/main/errors.c:1479
#4  0x743ed743 in _mesa_gl_debug (ctx=0x77fd1010, id=0x75b1e050
, source=MESA_DEBUG_SOURCE_API, type=MESA_DEBUG_TYPE_OTHER, 
severity=MESA_DEBUG_SEVERITY_MEDIUM, fmtString=0x752e743d "FBO
incomplete: %s [%d]\n") at src/mesa/main/errors.c:1493
#5  0x744236b4 in fbo_incomplete (ctx=0x77fd1010,
msg=0x752e77a2 "no attachments", index=-1) at src/mesa/main/fbobject.c:645
#6  0x7442462e in _mesa_test_framebuffer_completeness
(ctx=0x77fd1010, fb=0x1056f70) at src/mesa/main/fbobject.c:1192
#7  0x74431aeb in update_framebuffer (ctx=0x77fd1010, fb=0x1056f70)
at src/mesa/main/framebuffer.c:681
#8  0x74431b6d in _mesa_update_framebuffer (ctx=0x77fd1010,
readFb=0x1056f70, drawFb=0x1056f70) at src/mesa/main/framebuffer.c:707
#9  0x7446b364 in _mesa_update_state_locked (ctx=0x77fd1010) at
src/mesa/main/state.c:436
#10 0x7446b4e9 in _mesa_update_state (ctx=0x77fd1010) at
src/mesa/main/state.c:504
#11 0x74483762 in teximage (ctx=0x77fd1010, compressed=0 '\000',
dims=2, target=3553, level=0, internalFormat=33326, width=16, height=16,
depth=1, border=0, 
format=6403, type=5126, imageSize=0, pixels=0x0) at
src/mesa/main/teximage.c:2943
#12 0x74483a7f in _mesa_TexImage2D (target=3553, level=0,
internalFormat=33326, width=16, height=16, border=0, format=6403, type=5126,
pixels=0x0)
at src/mesa/main/teximage.c:3005
#13 0x00637262 in _get_glTexImage2D (target=3553, level=0,
internalformat=33326, width=16, height=16, border=0, format=6403, type=5126,
pixels=0x0)
at dispatch/glproc.cpp:7138
#14 0x004a673b in retrace_glTexImage2D (call=...) at
retrace/glretrace_gl.cpp:486
#15 0x00443bf4 in retrace::Retracer::retrace (this=0x9eea40 ,
call=...) at retrace/retrace.cpp:157
#16 0x00433cce in retrace::retraceCall (call=0x1057800) at
retrace/retrace_main.cpp:233
#17 0x00436330 in retrace::RelayRunner::runLeg (this=0xa4c7a0,
call=0x1057800) at retrace/retrace_main.cpp:386
#18 0x00436277 in retrace::RelayRunner::runRace (this=0xa4c7a0) at
retrace/retrace_main.cpp:364
#19 0x004340f4 in retrace::RelayRace::run (this=0x7fffd9a0) at
retrace/retrace_main.cpp:505
#20 0x00434347 in retrace::mainLoop () at retrace/retrace_main.cpp:565
#21 0x00434c9b in main (argc=2, argv=0x7fffdb88) at
retrace/retrace_main.cpp:880

It seems a bug in Mesa -- I don't know why it feels the need to check fbo
completness inside a glTexImage -- it makes no sense.  glTexImage is not a
draw/blit call.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

--- Comment #55 from har...@gmx.de ---
(In reply to Nicolai Hähnle from comment #53)
> The 'FBO incomplete' message is something that is often seen with apitrace.
> Not sure where it actually comes from, but in other cases it doesn't cause
> problems.

Yes, but it is at least confusing and i think it could be worth to be
investigated.

> Do you get a crash when you replay that trace file? If so, please provide
> the last couple of lines of output from `glretrace -v ` together
> with the backtrace. Also, if you do get a crash with the replay as well,
> running it in Valgrind may be helpful.

I never observed a crash while replaying apitrace files, not from successfull
runs (fno-inline-small-functions) nor from crashed runs
(finline-small-functions).

I just now updated to latest git (and simultanous an WT client update arrived).
Now the situation has changed:

- with finline-small-functions: it dosn't crash, but now it draws a lot of
funny textured polygons where they shouldn't be drawn.

- with fno-inline-small-functions: it works still flawless

If i undo some of the latest mesa commits, i got the old behavoir (crashes).

> Regarding your comment about Valgrind, please clarify: You ran War Thunder
> in Valgrind, and did get error reports from Valgrind but none of them in
> Mesa? Is that correct?

Yes, if i am running WT under valgrind (memcheck) i get some less helpfull
warnings/errors like this:

==1893== Conditional jump or move depends on uninitialised value(s)
==1893==at 0x5990E56: XRefreshKeyboardMapping (in
/usr/lib/x86_64-linux-gnu/libX11.so.6.3.0)
==1893==by 0x18E0F6B: ??? (in /home/player/WarThunder/aces)
==1893==by 0xF03DC3: ??? (in /home/player/WarThunder/aces)
==1893==by 0xDE7595: ??? (in /home/player/WarThunder/aces)
==1893==by 0x7D2A85: ??? (in /home/player/WarThunder/aces)
==1893==by 0x41529D: ??? (in /home/player/WarThunder/aces)
==1893==by 0x64F986F: (below main) (in
/lib/x86_64-linux-gnu/libc-2.21.so)).  

The main problem with valgrind is, that it slows down (20-30x) and WT breaks
with something like 'freeze detected' before serious gl activity, at least
before it crashes normally.

Do you think it would simplify things, if you download WT and try to run it
locally (it is free off charge)?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

--- Comment #52 from bellamort...@gmail.com ---
Of course I used the latest mesa git.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

--- Comment #53 from Nicolai Hähnle  ---
The 'FBO incomplete' message is something that is often seen with apitrace. Not
sure where it actually comes from, but in other cases it doesn't cause
problems.

Do you get a crash when you replay that trace file? If so, please provide the
last couple of lines of output from `glretrace -v ` together with
the backtrace. Also, if you do get a crash with the replay as well, running it
in Valgrind may be helpful.

Regarding your comment about Valgrind, please clarify: You ran War Thunder in
Valgrind, and did get error reports from Valgrind but none of them in Mesa? Is
that correct?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

--- Comment #50 from Nicolai Hähnle  ---
We clearly need more info. Please try with latest Mesa master. Does the crash
still depend on compiler optimizations? Have you tried running in Valgrind as
Roland suggested?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

--- Comment #49 from bellamort...@gmail.com ---
Still occurs with GCC 5.3

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

--- Comment #51 from har...@gmx.de ---
This bug is still present with latest master and still depends on compiler
optimization as described. I have done a run with valgrind, but the results are
not very helpful, WT is not open source and there are no debug symbols
available.

Here is a newer apitrace file (still a lot of garbage is drawn while
replaying).

http://www34.zippyshare.com/v/WmlopiNi/file.html


In frame #0, call #627 (glTexImage2D) an error occures 'api issue 1: FBO
incomplete: no attachments [-1]'.

(For my understanding, this call should reserve/allocate GPU memory for a 16x16
texture)

Maybe there is a relation to garbage drawing in apitrace and perhaps to this
bug?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

--- Comment #48 from higu...@gmx.net ---
-O3 -fno-inline-small-functions  also works for me

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

--- Comment #47 from higu...@gmx.net ---
well, I also having crash in warthunder... i'm using slackware64, kernel 4.3.0
llvm 3.7.0 and mesa 11.1-rc2 and after applying the patch from Bug 92709 to fix
the "unsupported call to function ldexpf in main" and recompile, it crash with
a core dump, with this backtrace:

Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7f401499ae18 in glsl_to_tgsi_visitor::visit(ir_expression*) () from
/usr/lib64/xorg/modules/dri/radeonsi_dri.so
[Current thread is 1 (Thread 0x7f401a951700 (LWP 20315))]
(gdb) bt
#0  0x7f401499ae18 in glsl_to_tgsi_visitor::visit(ir_expression*) () from
/usr/lib64/xorg/modules/dri/radeonsi_dri.so
#1  0x7f401499ada9 in glsl_to_tgsi_visitor::visit(ir_expression*) () from
/usr/lib64/xorg/modules/dri/radeonsi_dri.so
#2  0x7f401499186c in glsl_to_tgsi_visitor::try_emit_mad(ir_expression*,
int) () from /usr/lib64/xorg/modules/dri/radeonsi_dri.so
#3  0x7f401499af50 in glsl_to_tgsi_visitor::visit(ir_expression*) () from
/usr/lib64/xorg/modules/dri/radeonsi_dri.so
#4  0x7f401499ada9 in glsl_to_tgsi_visitor::visit(ir_expression*) () from
/usr/lib64/xorg/modules/dri/radeonsi_dri.so
Backtrace stopped: Cannot access memory at address 0x7f401a906318


LIBGL_DEBUG=verbose don't show anything special

If i also recompile with the -O0, it works, so looks now i'm hitting this bug.
I'm using gcc 5.2.0

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

--- Comment #45 from har...@gmx.de ---
Created attachment 120336
  --> https://bugs.freedesktop.org/attachment.cgi?id=120336=edit
backtrace with activated -finline-small-functions

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

--- Comment #46 from har...@gmx.de ---
here is the code from ir.h where it fails:


   /**
* Determine the number of operands used by an expression
*/
   static unsigned int get_num_operands(ir_expression_operation);

   /**
* Determine the number of operands used by an expression
*/
   unsigned int get_num_operands() const
   {
  return (this->operation == ir_quadop_vector)
 ? this->type->vector_elements : get_num_operands(operation);
   }


Is it strange enough to fail if compiled inline in this code below?


   for (operand = 0; operand < ir->get_num_operands(); operand++) {
  this->result.file = PROGRAM_UNDEFINED;
  ir->operands[operand]->accept(this);
  if (this->result.file == PROGRAM_UNDEFINED) {
 printf("Failed to get tree for expression operand:\n");
 ir->operands[operand]->print();
 printf("\n");
 exit(1);
  }
  op[operand] = this->result;

  /* Matrix expression operands should have been broken down to vector
   * operations already.
   */
  assert(!ir->operands[operand]->type->is_matrix());
   }

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

--- Comment #44 from har...@gmx.de ---
(In reply to bellamorte42 from comment #40)
> compiling with -O3 -fno-inline-small-functions works.

yep, i can confirm that '-finline-small-functions' is the black sheep.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

--- Comment #43 from Roland Scheidegger  ---
(In reply to bellamorte42 from comment #42)
> I'm not sure I follow your logic.  The code compiles fine on its own.  The
> code compiles fine under a variety of optimizations.  A single optimization
> causes a segfault. =it's the codes fault?
Why not? Things like that are quite common. For instance when using undefined
values it can easily work with some compiler options but not others. Or doing
some kind of reading/writing past array bounds. All bets are off with such code
(and valgrind would catch both these errors). Not saying that's necessarily the
case here but I don't see any evidence to the contrary neither...

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

--- Comment #35 from har...@gmx.de ---
I found that only CXXFLAGS do the trick.

If i append CXXFLAGS='-O1' to the configure params, WT works flawless.

Since 'st_glsl_to_tgsi.cpp' is the only .cpp file in folder 'state_tracker', it
seems to make sense to assume the problem here.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

--- Comment #39 from bellamort...@gmail.com ---
Ugh, bisection is done.
CXXFLAG -finline-small-functions cuases the segfault.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

--- Comment #40 from bellamort...@gmail.com ---
compiling with -O3 -fno-inline-small-functions works.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

--- Comment #41 from Roland Scheidegger  ---
miscompilations are possible but rare, often different compiler options just
hide a bug. Did you try running this with valgrind?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

--- Comment #36 from har...@gmx.de ---
i can now confirm:

Compiling only file 'st_glsl_to_tgsi.cpp' with '-O1' and everything else with
default '-O2' works flawless.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

--- Comment #37 from bellamort...@gmail.com ---
Confirmed that -O3 CFLAGS and -O1 CXXFLAGS works.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

--- Comment #42 from bellamort...@gmail.com ---
I'm not sure I follow your logic.  The code compiles fine on its own.  The code
compiles fine under a variety of optimizations.  A single optimization causes a
segfault. =it's the codes fault?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

--- Comment #38 from har...@gmx.de ---
@bellamorte,

for better performance of this workaround, you could try the following:

1. make clean
2. generate 'makefile' via 'autogen.sh' with your prefered settings
3. make
4. delete 'src/mesa/state_tracker/st_glsl_to_tgsi.lo'
5. generate 'makefile' via 'autogen.sh' with CXXFLAGS='-O1'
6. make (only st_glsl_to_tgsi.cpp will be compiled)
7. install as usual

... that is what works for me ...

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

--- Comment #31 from bellamort...@gmail.com ---
Sorry, here's the full list.
CFLAGS="-march=bdver2 -O1 -pipe -fstack-protector-strong
--param=ssp-buffer-size=4"
CXXFLAGS="-march=bdver2 -O1 -pipe -fstack-protector-strong
--param=ssp-buffer-size=4"

And as I said, -O0 and -O1 works with the rest of what's there but -O3 does
not.  I'll give your suggestion a try a soon as I can.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

Tapani Pälli  changed:

   What|Removed |Added

 CC|lem...@gmail.com|

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

--- Comment #34 from Michel Dänzer  ---
The gcc manual has a list of all -f... options enabled by -O2. You can try
bisecting that list to find the individual -f... option which triggers the
problem.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

--- Comment #32 from bellamort...@gmail.com ---
-fno-strict-aliasing with -O3 still segfaults.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

--- Comment #33 from bellamort...@gmail.com ---
-O2 segfaults

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

Michel Dänzer  changed:

   What|Removed |Added

  Component|Drivers/Gallium/radeonsi|Mesa core
   Assignee|dri-devel@lists.freedesktop |mesa-dev@lists.freedesktop.
   |.org|org
 QA Contact|dri-devel@lists.freedesktop |mesa-dev@lists.freedesktop.
   |.org|org

--- Comment #28 from Michel Dänzer  ---
Sounds like some code in st_glsl_to_tgsi.cpp is getting miscompiled with
optimization. Is compiling only that file with -O0 enough to avoid the problem?

What optimization flags are being used normally?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

--- Comment #29 from bellamort...@gmail.com ---
Well that was quick.  Not done testing it yet.  First test run was done with
-march=bdver2 and -O0.  That worked. Second one was done with -march=bdver2 and
-O1. That worked.  Orginally I was using -O3 and didn't hit any issues until
war thunder.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 92850] Segfault loading War Thunder

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=92850

--- Comment #30 from Michel Dänzer  ---
Is -fno-strict-aliasing included in the final flags passed to the compiler? If
not, does adding that help?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/mesa-dev