https://bugs.freedesktop.org/show_bug.cgi?id=108933
Timothy Arceri changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=108933
--- Comment #14 from i...@yahoo.com ---
I'm still puzzled by a number of things related to this bug and the export of
"__dynamic_cast".
If I rename it to "__dyn_cast_old" in Core.so, the game exits with "undefined
__dyn_cast_old". It does so dur
https://bugs.freedesktop.org/show_bug.cgi?id=108933
--- Comment #13 from network...@rkmail.ru ---
(In reply to Gustaw Smolarczyk from comment #12)
> On a slightly unrelated topic, UT99 seems to work fine (at least for me)
> while run on wine (or Steam's proton). You might want to try this path as
https://bugs.freedesktop.org/show_bug.cgi?id=108933
--- Comment #12 from Gustaw Smolarczyk ---
(In reply to iive from comment #10)
> You solved the mystery!
>
> It makes sense since this is the last called function in the disassembly.
>
> I can confirm that the issue does go away after changing
https://bugs.freedesktop.org/show_bug.cgi?id=108933
--- Comment #11 from i...@yahoo.com ---
(In reply to iive from comment #10)
> I can confirm that the issue does go away after changing the string
> "__dynamic_cast" to "__dynamicZcast" in Core.so .
That doesn't work. It is enough for the game t
https://bugs.freedesktop.org/show_bug.cgi?id=108933
--- Comment #10 from i...@yahoo.com ---
(In reply to Gustaw Smolarczyk from comment #9)
> The Core.so binary seems to export the __dynamic_cast symbol. It suggests
> that it has been statically linked with some old libstdc++ library that is
> inc
https://bugs.freedesktop.org/show_bug.cgi?id=108933
--- Comment #9 from Gustaw Smolarczyk ---
(In reply to iive from comment #8)
> I've already tried placing "#include " before "iostream", but it has
> no effect. I retested it to be sure.
That won't do anything. The locale stuff is handled by li
https://bugs.freedesktop.org/show_bug.cgi?id=108933
--- Comment #8 from i...@yahoo.com ---
(In reply to Gustaw Smolarczyk from comment #7)
> Static initialization order is undefined between translation units (i.e.
> source files) but it is defined within one translation unit - it is the
> global v
https://bugs.freedesktop.org/show_bug.cgi?id=108933
--- Comment #7 from Gustaw Smolarczyk ---
Static initialization order is undefined between translation units (i.e. source
files) but it is defined within one translation unit - it is the global
variable definition order. Since #include defines
https://bugs.freedesktop.org/show_bug.cgi?id=108933
--- Comment #6 from i...@yahoo.com ---
Created attachment 142752
--> https://bugs.freedesktop.org/attachment.cgi?id=142752&action=edit
Workaround for mesa crashing on UT99 because of static global constructor from
C++ iostream
Just few observa
https://bugs.freedesktop.org/show_bug.cgi?id=108933
--- Comment #5 from i...@yahoo.com ---
The upgrade was from gcc-7.3.0 to gcc-8.2.0. You can see 8.2.0 include in the
backtrace.
I don't think that we can blame gcc-8.2.0 for the redhat bugreport, as they do
use a development snapshot. (Now stabl
https://bugs.freedesktop.org/show_bug.cgi?id=108933
--- Comment #4 from Michel Dänzer ---
Which version of g++/gcc are you using? Some 8.2 snapshots have a bug which
causes mis-compilation of Mesa code:
https://bugzilla.redhat.com/show_bug.cgi?id=1645400
--
You are receiving this mail because:
https://bugs.freedesktop.org/show_bug.cgi?id=108933
--- Comment #3 from i...@yahoo.com ---
I got the UT99 working.
valgrind doesn't show anything more, the first error is the one from the
report.
When trying to narrow mesa releases that work, I got mesa-18.1.7 working and
mesa-18.2.0 not workin
https://bugs.freedesktop.org/show_bug.cgi?id=108933
--- Comment #2 from network...@rkmail.ru ---
Created attachment 142739
--> https://bugs.freedesktop.org/attachment.cgi?id=142739&action=edit
valgrind log
(In reply to iive from comment #1)
> 1. See if changing your locale has effect on the cra
https://bugs.freedesktop.org/show_bug.cgi?id=108933
--- Comment #1 from i...@yahoo.com ---
Mesa developers need to be able to reproduce the problem and they are not going
to install UT to debug this. So we'll have to do a bit more investigating on
this one.
There are few things for you to try:
https://bugs.freedesktop.org/show_bug.cgi?id=108933
Bug ID: 108933
Summary: Unreal Tournament (UT99) segfault on opengl init
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: normal
16 matches
Mail list logo
