From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] mesa 11.0.9-2
Date: Mon, 06 Jun 2016 07:25:00 -0000 [thread overview]
Message-ID: <dc6a9435-58ca-36fd-8fa6-4f9da0b49b81@cygwin.com> (raw)
In-Reply-To: <4311402a-fb7d-c68a-9cb3-954161a37e58@dronecode.org.uk>
On 2016-06-03 12:56, Jon Turney wrote:
> On 31/05/2016 18:03, Jon Turney wrote:
>> On 13/04/2016 03:33, Yaakov Selkowitz wrote:
>>> On 2016-04-12 10:20, Marco Atzeri wrote:
>>>> $ cd /usr/lib/mesa-demos
>>>> $ ./quad-clip.exe
>>>> GL_RENDERER = Gallium 0.4 on llvmpipe (LLVM 3.7, 256 bits)
>>>> GL_VERSION = 3.0 Mesa 11.0.9
>>>> GL_VENDOR = VMware, Inc.
>>>> Segmentation fault (core dumped)
>>>
>>> I can reproduce this on 32-bit but not 64-bit, and the same happens with
>>> 11.1.2. It may be an issue with LLVM 3.7 (11.0.9-1 was built with 3.5)
>>> but without a useful backtrace it will be hard to pin down.
>>
>> gdb can successfully backtrace this, with today's cygwin snapshot.
>>
>> Both examples of the crash provided by Marco show very similar symptoms.
>>
>> Unfortunately, the backtrace stops at llvm_pipeline_generic() calling
>> into some JIT-ed code. The faulting is at an insertps instruction with
>> what looks like a bogus absolute address.
>>
>> So I guess this some is an llvm issue, possibly with some address
>> computation which doesn't give the right result on 32 bit?
>>
>>> # gdb ./quad-clip
>>> [...]
>>> (gdb) r
>>> [...]
>>> Program received signal SIGSEGV, Segmentation fault.
>>> 0x7fdf00c1 in ?? ()
> [...]
>>> /usr/src/debug/mesa-demos-8.3.0-1/src/trivial/quad-clip.c:137
>>> (gdb) disassemble 0x7fdf00b1,0x7fdf00d2
>>> Dump of assembler code from 0x7fdf00b1 to 0x7fdf00d2:
>>> 0x7fdf00b1: insertps $0x10,0x4(%eax,%edi,1),%xmm0
>>> 0x7fdf00b9: insertps $0x20,0x8(%eax,%edi,1),%xmm0
>>> => 0x7fdf00c1: insertps $0x30,0xfffeff34,%xmm0
>>> 0x7fdf00cb: mov (%esi),%eax
>>> 0x7fdf00cd: mul %ecx
>
> After staring this a bit more, I see that this is the offset to the data
> to load, apparently being used as an absolute address
>
> This seems to be the case with other addresses in the JIT-ed code, so
> perhaps there is some problem preventing relocations being applied...
FWIW, I tried rebuilding with llvm 3.8.0. 32-bit doesn't crash anymore,
and glxgears says its running, but only the background shows.
--
Yaakov
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2016-06-06 7:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 9:08 Yaakov Selkowitz
2016-04-12 15:20 ` Marco Atzeri
2016-04-13 2:17 ` gdb using Windows paths in dlopen()ed modules? Yaakov Selkowitz
2016-04-13 8:09 ` Corinna Vinschen
2016-04-13 2:33 ` [ANNOUNCEMENT] mesa 11.0.9-2 Yaakov Selkowitz
2016-05-25 13:56 ` Marco Atzeri
[not found] ` <b8ee7d32-504d-27d8-51ab-547ea7a51968@dronecode.org.uk>
2016-06-03 17:56 ` Jon Turney
2016-06-06 7:25 ` Yaakov Selkowitz [this message]
2016-06-06 14:27 ` Jon Turney
2016-06-09 22:01 ` [ANNOUNCEMENT] mesa 11.0.9-2 [GOLDSTAR] Yaakov Selkowitz
2016-06-10 4:36 ` Marco Atzeri
2016-06-10 8:31 ` Corinna Vinschen
2016-06-10 14:49 ` Andrew Schulman
2016-06-20 18:29 ` Jon Turney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dc6a9435-58ca-36fd-8fa6-4f9da0b49b81@cygwin.com \
--to=yselkowitz@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).