[Bug 250448] emulators/qemu-user-static: fails to run devel/llvm10 on 12.1/12.2 aarch64

[email protected]
Newsgroups gmane.os.freebsd.devel.x11
Message-ID <[email protected]/bugzilla/>
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250448

Jan Beich <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|emulators/qemu-user-static: |emulators/qemu-user-static:
                   |fails to run devel/llvm10   |fails to run devel/llvm10
                   |on 12.1 aarch64             |on 12.1/12.2 aarch64

--- Comment #4 from Jan Beich <[email protected]> ---
(In reply to Kyle Evans from comment #2)
In my case:
- 13.0-CURRENT amd64 host, built 2 days ago
- 13.0-CURRENT aarch64 jail, built on 2020-09-01
- 12.2-RC3 aarch64 jail, built today
- 12.1-RELEASE aarch64 jail, built on 2019-11-05

All jails built with -x (native-xtools).

(In reply to Jan Beich from comment #1)
> (haven't tried 11.4 and 12.2)

llvm10 crashes on 12.2 as well:

$ llvm-config10
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
Segmentation fault
$ clang10
Stack dump:
0.      Program arguments: /usr/local/llvm10/bin/clang
0  libLLVM-10.so 0x00000040064070c8
llvm::sys::PrintStackTrace(llvm::raw_ostream&) + 68
1  libLLVM-10.so 0x00000040064053f8 llvm::sys::RunSignalHandlers() + 128
2  libLLVM-10.so 0x0000004006407a3c
llvm::sys::PrintStackTraceOnErrorSignal(llvm::StringRef, bool) + 1596
3  libthr.so.3   0x0000004002044f9c _pthread_sigmask + 1316
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
Segmentation fault

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-x11
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.