From: | Wen Yi <wen-yi(at)qq(dot)com> |
---|---|
To: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | [Beginner Question] How to print the call link graph? |
Date: | 2023-07-01 07:10:27 |
Message-ID: | tencent_AAA2992A43F2C4A5BBE9486BB888D449AD0A@qq.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi community,
I use the gdb to track the postgres like this:
...
pq_getbyte () at pqcomm.c:980
980 in pqcomm.c
(gdb) next
985 in pqcomm.c
(gdb) next
986 in pqcomm.c
(gdb) next
SocketBackend (inBuf=0x7ffc8f7e1310) at postgres.c:372
372 postgres.c: Directory not empty.
(gdb) next
403 in postgres.c
(gdb) next
406 in postgres.c
(gdb) next
407 in postgres.c
(gdb) next
...
But the question is:
It's too slow to input 'next' to run the postgres, I used to try to use the 'continut', but the gdb will run the postgres directly and not print the function name and code line
I want to it print like this:
... -> pq_getbyte () at pqcomm.c:980 -> SocketBackend (inBuf=0x7ffc8f7e1310) at postgres.c:372 -> ...
Can someone provide me some advice?
Thanks in advance!
Yours,
Wen Yi
From | Date | Subject | |
---|---|---|---|
Next Message | Ron | 2023-07-01 15:26:07 | Re: [Beginner Question] How to print the call link graph? |
Previous Message | Julien Rouhaud | 2023-07-01 06:06:57 | Re: psql and pgpass.conf on Windows |