public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jose Isaias Cabrera <jicman@outlook.com>
To: Agner Fog <agner@agner.org>, "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Bug report. Clang sqrtl(-1) causes access violation
Date: Fri, 10 May 2019 19:54:00 -0000	[thread overview]
Message-ID: <DB7PR01MB538645A4A3A507A493B098D0DE0C0@DB7PR01MB5386.eurprd01.prod.exchangelabs.com> (raw)
In-Reply-To: <03f2a425-2f3f-4230-c4c5-3265f511d4f5@agner.org>


Agner Fog, on Friday, May 10, 2019 03:44 PM, wrote...
>
>On 10/05/2019 15.50, Jose Isaias Cabrera wrote:
>
>> It works for me.
>
>Now it turns out that all the long double math functions cause access
>violations.
>
>If you can't reproduce the error, what can I do to trace it?
>
>
>Exception: STATUS_ACCESS_VIOLATION at rip=00180173164

Sounds to me like there are some damaged DLL or something.  Can you do a,

uname -a

and send us the output.  Also, please do a,

clang --version

and show us your output.  You may need to do a rebaseall, but first, let's see what versions you are running. Thanks.

josé

--
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

  reply	other threads:[~2019-05-10 19:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-10 12:58 Agner Fog
2019-05-10 13:38 ` Sam Habiel
2019-05-10 14:04   ` Franz Fehringer
2019-05-10 13:50 ` Jose Isaias Cabrera
2019-05-10 19:44   ` Agner Fog
2019-05-10 19:54     ` Jose Isaias Cabrera [this message]
2019-05-10 20:56       ` Agner Fog
2019-05-11  3:33         ` Jose Isaias Cabrera
2019-06-03 11:11 ` Corinna Vinschen

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=DB7PR01MB538645A4A3A507A493B098D0DE0C0@DB7PR01MB5386.eurprd01.prod.exchangelabs.com \
    --to=jicman@outlook.com \
    --cc=agner@agner.org \
    --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).