Re: BUG #18503: Reproducible 'Segmentation fault' in 16.3 on ARM64
От | Thomas Munro |
---|---|
Тема | Re: BUG #18503: Reproducible 'Segmentation fault' in 16.3 on ARM64 |
Дата | |
Msg-id | CA+hUKG+8a_NOUbNFuboqh6DLBb5m3AnmaqB4fg4w4SZHi3Hs4g@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: BUG #18503: Reproducible 'Segmentation fault' in 16.3 on ARM64 (Stefan Heine <github.stheine@heine7.de>) |
Ответы |
Re: BUG #18503: Reproducible 'Segmentation fault' in 16.3 on ARM64
Re: BUG #18503: Reproducible 'Segmentation fault' in 16.3 on ARM64 |
Список | pgsql-bugs |
On Thu, Jun 13, 2024 at 1:47 AM Stefan Heine <github.stheine@heine7.de> wrote: > do you have instructions for the gdb backtrace? gdb /path/to/executable -c /path/to/core ... loads stuff ... (gdb) bt ... prints out function call stack ... It will probably just show some library names and addresses, but so far we don't even know if this is crashing in LLVM or in PostgreSQL code so that'd be a clue. Maybe function names would appear if you set up DEBUGINFOD_URLS, depending on where you got your packages from: https://wiki.debian.org/HowToGetABacktrace Hoping to find time to repro this later on a cloud host. If this is a cloud host, can you tell me which cloud, instance type, memory size etc? I had already been trying on some local ARM hardware with no luck (same versions but diferrent OS, so going to try making more things match you case)...
В списке pgsql-bugs по дате отправления: