Re: BUG #16665: Segmentation fault
I'm not really sure how to read that binary file.
I have uploaded to an s3 bucket and made it public.
Anyone should be able to access that file
it's 2GB
If you have a link to a documentation of how I can read that file and get the stacktrace, I would be glad to give it a read.
On Saturday, Oct 10, 2020 at 8:56 PM, Pavel Stehule <pavel.stehule@gmail.com> wrote:so 10. 10. 2020 v 13:27 odesílatel Raphael Megzari <raphael@megzari.com> napsal:Awesome, thank you!It's the right thing.How do I share it?important is the backtracepaste it to mailOn Saturday, Oct 10, 2020 at 8:24 PM, Pavel Stehule <pavel.stehule@gmail.com> wrote:so 10. 10. 2020 v 13:19 odesílatel Raphael Megzari <raphael@megzari.com> napsal:Thank you for taking the time to have a look.I'm not sure how to enable core dump with the docker image.I've seen some documentation where the db is started with pg_ctl anc a "c" flag. I couldn't find anything on enabling it on the docker image.in my data folder, I have a huge core file (8 GB). Would it be possible that it is the core dump file generated after the segfault?you can check a create timePavelRaphaelOn Saturday, Oct 10, 2020 at 6:04 PM, Pavel Stehule <pavel.stehule@gmail.com> wrote:Hi
If I can help in any ways, please let me know.
I don't mind trying things, like I said, the bug happens about every 2
days.This is a bug, but from your bug report isn't possible to detect any information.Can you enable core dump generating, and can you send a core dump?RegardsPavel
Cheers!
В списке pgsql-bugs по дате отправления: