25.3 Stable - Symbol table is missing from stripped build #1183
Description
✅ I checked the Altinity Stable Builds lifecycle table, and the Altinity Stable Build version I'm using is still supported.
Type of problem
Usability issue - something works, but it could be a lot easier
Describe the situation
The stripped build does not contain the symbol table. Stack traces contain question marks.
Upstream did not release a stripped build for 25.3.
How to reproduce the behavior
$ wget https://builds.altinity.cloud/bin-repo/amd64/v25.3.6.10034.altinitystable/non-self-extracting/clickhouse-stripped
$ nm clickhouse-stripped
nm: clickhouse-stripped: no symbols
Expected behavior
Stack trace should have readable function names even in the stripped build.
Logs, error messages, stacktraces, screenshots...
$ ./clickhouse-stripped local --stacktrace --query "select throwIf(1, 'foo')"
Code: 395. DB::Exception: foo: while executing 'FUNCTION throwIf(1_UInt8 :: 1, 'foo'_String :: 2) -> throwIf(1_UInt8, 'foo'_String) UInt8 : 3'. (FUNCTION_THROW_IF_VALUE_IS_NON_ZERO), Stack trace (when copying this message, always include the lines below):
0. ? @ 0x000000000f52449b
1. ? @ 0x000000000e451b2c
2. ? @ 0x000000000e45064a
3. ? @ 0x0000000011c2121a
4. ? @ 0x0000000011c1a521
5. ? @ 0x0000000011c1b9be
6. ? @ 0x0000000011c1cd1b
7. ? @ 0x0000000013255219
8. ? @ 0x0000000015067a16
9. ? @ 0x0000000011632f73
10. ? @ 0x0000000014dca595
11. ? @ 0x0000000014de8796
12. ? @ 0x0000000014ddc284
13. ? @ 0x0000000014ddb45e
14. ? @ 0x0000000014debf38
15. ? @ 0x000000000f6568af
16. ? @ 0x000000000f65db7a
17. ? @ 0x000074e2d5094ac3
18. ? @ 0x000074e2d51268c0
Job's origin stack trace:
0. ? @ 0x000000000f65e7b7
1. ? @ 0x000000000f657b98
2. ? @ 0x0000000014deac73
3. ? @ 0x0000000014deb1b9
4. ? @ 0x0000000014c33f03
5. ? @ 0x0000000014bc6e53
6. ? @ 0x0000000014bc41c0
7. ? @ 0x0000000014bcfd2a
8. ? @ 0x0000000014bd1650
9. ? @ 0x0000000014bdb33b
10. ? @ 0x000000000f808d74
11. ? @ 0x000000001849e146
12. ? @ 0x000000000f816a0f
13. ? @ 0x0000000009fc0a81
14. ? @ 0x000074e2d5029d90
15. ? @ 0x000074e2d5029e40
16. ? @ 0x0000000006b8d02e
Additional context
This issue is likely present in other releases.