Azat Khuzhin 25e3bebd9d Rework core collecting on CI (eliminate gcore usage) ... gcore is a gdb command, that internally uses gdb to dump the core. However with proper configuration of limits (core_dump.size_limit) it should not be required, althought some issues is possible: - non standard kernel.core_pattern - sanitizers So yes, gcore is more "universal" (you don't need to configure any `kernel_pattern`), but it is ad-hoc, and it has drawbacks - **it does not work when gdb fails**. For example gdb may fail with `Dwarf Error: DW_FORM_strx1 found in non-DWO CU` in case of DWARF-5 [1]. [1]: https://github.com/ClickHouse/ClickHouse/pull/40772#issuecomment-1236331323. Let's try to switch to more native way. Signed-off-by: Azat Khuzhin <a.khuzhin@semrush.com>		2022-09-04 22:07:16 +02:00
..
Dockerfile
generate-test-j2.py
query-fuzzer-tweaks-users.xml
run-fuzzer.sh	Rework core collecting on CI (eliminate gcore usage)	2022-09-04 22:07:16 +02:00