or starting it normally and then attaching GDB (having found the PID with a select pg_backend_pid() ):
gdb -p <PID>
I can't get to set a breakpoint in crypt.c, for example. It theoretically loaded debugging symbols, but I can't find the .c files inside the src/ from where I built Postgres. If I try to add them:
The address where software/postgres_dec6e47/src/backend/libpq/crypt.c has been loaded is missing
I suspect this has something to do with postgres having to be launched with user postgres, while gdb not, besides installing it from my normal user and not postgres. When trying to build it with postgres user, it basically complains about it not being in sudoers.
On the other hand, I tried to set up logging and I did not get any further info.
Thanks.
Julián Jiménez González
Investigador - Desarrollador | Área de Servicios y Aplicaciones
Researcher - Developer | Services & Applications Department
Take care of the environment. Try not to print this email. The information contained in this email message may be confidential information, and may also be the subject of legal professional privilege. If you are not the intended recipient, any use, interference with, disclosure or copying of this material is unauthorized and prohibited. Please inform us immediately and destroy the email. Thank you for your cooperation.
2018-02-22 10:55 GMT+01:00 Christoph Berg <myon@debian.org>:
Re: Julián Jiménez González 2018-02-21 <CAANxhjKZKWh-Rfdh=OvUPOmobKiSm54j9MdACeKOV=y_iiaHtw@mail.gmail.com> > I need and would greatly appreciate any help tracking this problem down.
I'd try setting gdb breakpoints on the relevant code lines/functions.