Bug 275784 - clang crashes on the port math/vtk8 on the arm64 architecture
Summary: clang crashes on the port math/vtk8 on the arm64 architecture
Status: Closed DUPLICATE of bug 264834
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: 13.2-STABLE
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-toolchain (Nobody)
URL: https://pkg-status.freebsd.org/ampere...
Keywords:
Depends on:
Blocks:
 
Reported: 2023-12-15 22:09 UTC by Yuri Victorovich
Modified: 2023-12-16 01:12 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Yuri Victorovich freebsd_committer freebsd_triage 2023-12-15 22:09:48 UTC 
The crashes only occur on 13.2 arm64.






1.	<eof> parser at end of file
2.	Optimizer
#0 0x000000000424d8a4 (/usr/bin/c+++0x424d8a4)
#1 0x000000000424bc18 (/usr/bin/c+++0x424bc18)
#2 0x000000000420195c (/usr/bin/c+++0x420195c)
#3 0x0000000088839480 (/lib/libthr.so.3+0x29480)
c++: error: clang frontend command failed with exit code 139 (use -v to see invocation)
FreeBSD clang version 14.0.5 (https://github.com/llvm/llvm-project.git llvmorg-14.0.5-0-gc12386ae247c)
Target: aarch64-unknown-freebsd13.2
Thread model: posix
InstalledDir: /usr/bin
c++: note: diagnostic msg: 
********************

PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
Preprocessed source(s) and associated run script(s) are located at:
c++: note: diagnostic msg: /tmp/vtkGeoInteractorStyle-889efa.cpp
c++: note: diagnostic msg: /tmp/vtkGeoInteractorStyle-889efa.sh
c++: note: diagnostic msg: 

********************
Comment 1 Dimitry Andric freebsd_committer freebsd_triage 2023-12-16 00:13:35 UTC 
Isn't this a dupe of bug 264834? It was solved in https://cgit.freebsd.org/src/commit/?id=91ec809f0a90798296697cfc9afdb1c50c6d4971 but that didn't make it into 13.2-RELEASE.

If there are many ports crashing with this issue, we might do an Erratum, but it might be easier to work around the crash, somehow?
Comment 2 Yuri Victorovich freebsd_committer freebsd_triage 2023-12-16 01:12:30 UTC 
Yes, this is a duplicate. Sorry that I didn't find it right away.

I am not aware of any other ports crashing for this reason.

Closing then.

*** This bug has been marked as a duplicate of bug 264834 ***