-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
Not a bug: libunwind: aarch64: SIGSEGV signal handler leads to another seg fault #63855
Comments
This is normal right now, because the SIGSEGV likely happened in unwind, and later on, it tries to unwind from almost the same stack, and it crashes on the same frame It is likely will be fixed by #60468 |
@azat No, tried yesterday, didn't help. |
Also #63865 didn't help as well |
Crash in libunwind - ARM64 (with today's master): https://s3.amazonaws.com/clickhouse-test-reports/64180/7123d08a692e98b71e87c3b24dde62d427ce410b/stateless_tests__aarch64_.html
The server crashes when generating a StackTrace |
This is actually a different problem, and it is more similar to #60460 |
Problem can be 100% reproduced in integration tests on ARM in TCs:
Stack trace:
libunwind fork commit: 40d8eadf96b127d9b22d53ce7a4fc52aaedea965
To reproduce manually (not in tests):
SELECT COUNT(*) FROM system.crash_log ==> 0
The text was updated successfully, but these errors were encountered: