From: Tom Lane <tgl@sss.pgh.pa.us>
To: clipperDB@gmx.fr
cc: pgsql-general@lists.postgresql.org
Subject: Re: printing PGresult content with gdb
In-reply-to: <trinity-3ee0d178-9734-4afd-8657-c348e860763e-1719936784801@3c-app-mailcom-bs16>
References: <trinity-3ee0d178-9734-4afd-8657-c348e860763e-1719936784801@3c-app-mailcom-bs16>
Comments: In-reply-to clipperDB@gmx.fr
	message dated "Tue, 02 Jul 2024 18:13:04 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3258156.1720022101.1@sss.pgh.pa.us>
Date: Wed, 03 Jul 2024 11:55:01 -0400
Message-ID: <3258157.1720022101@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/3258157.1720022101%40sss.pgh.pa.us>
Precedence: bulk

clipperDB@gmx.fr writes:
> I don't know if it is the right mailing list, but i was
> wondering if one could introspect via gdb the content of PGresult.

You might have better luck with that if you install the debuginfo
RPM corresponding to your libpq RPM.  PGresult's innards are not
exposed to applications by libpq-fe.h, so your own app's debug
data is not going to contain the details of the struct.  But I think
it would be available to gdb if libpq's debug symbols were installed.

			regards, tom lane