-
-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SIGSEGV on cygwin #283
Comments
The The regression test script should automatically print all the output from |
sorry, i forget to add appropriate
i'll do more check soonish...
b/c it looks SIGSEGV. |
FYI,
it looks using
as i reported above, it looks
update: add trace log. |
I think the I guess this happens running any simulation? What version of llvm? |
maybe, yes.
|
I tried with LLVM 3.7 on Linux and don't get this failure. Is it possible to try with another LLVM version on Cygwin that was known to work? |
LLVM 3.5 looks working on cygwin.
|
There's some code in |
as you mentioned about and here's weird result, it looks NVC fails to run if
|
I think the I'll try this on a Windows PC later in the week, see if I can figure out what's going on... |
I also get the same crash on 64-bit Windows 10, but I didn't make much progress debugging it. Are you using 64-bit Windows too? It's possibly related to this: https://llvm.org/bugs/show_bug.cgi?id=24978 |
yes, i'm on Windows 10 Pro 64bit w/ Cygwin x86. |
FYI,
w/ above dirty change, most of regressions look ok even on Windows 10 Pro 64bit w/ Cygwin x86.
|
FYI,
using faild regressions for 3.8.1 are same ones for 3.7.1; |
Can you try the the current |
I tried
the last command
|
What if you revert that patch though? For me with LLVM 3.9 on MSYS2 the JIT works OK (but not loading native libraries). |
using |
Just as an update on this bug, the latest master now more-or-less works on Cygwin with modern LLVM. There are still a few test failures though. |
yes, it looks you made NVC better. |
Cygwin should be fully working again now, and it's checked on every commit on AppVeyor: |
i got,
to check why
wait1
failed, run its regression manually, and i got,update: oops, submitted draft accidentally. :)
The text was updated successfully, but these errors were encountered: