external
/
citus
mirror of https://github.com/citusdata/citus.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

print instructions on how to disable the breakpoint from the debug console in vscode

pull/7279/head
Nils Dijk 2023-10-27 13:17:15 +00:00
parent 5bbf46ebb8
commit 8323e5393c
1 changed files with 12 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
.devcontainer/.gdbinit
View File

@ -16,10 +16,18 @@ source /root/gdbpg.py
# ERROR symbol so we hardcode this to the value of ERROR. It is very unlikely
# this value will ever change in postgres, but if it does we might need to
# find a way to conditionally load the correct breakpoint.
# Lastly the breakpoint doesn't show up in vscode :(, to remove the breakpoint
# you can use the command `-exec delete <id>` in the vscode debug console. The
# id is the number in the first column of the breakpoint list which you can
# show with the command `-exec info break`.
set breakpoint pending on
break elog.c:errfinish if errordata[errordata_stack_depth].elevel == 21
set breakpoint pending auto
echo \n
echo ----------------------------------------------------------------------------------\n
echo when attaching to a postgres backend a breakpoint will be set on elog.c:errfinish \n
echo it will only break on errors being raised in postgres \n
echo \n
echo to disable this breakpoint from vscode run `-exec disable 1` in the debug console \n
echo this assumes it's the first breakpoint loaded as it is loaded from .gdbinit \n
echo this can be verified with `-exec info break`, enabling can be done with \n
echo `-exec enable 1` \n
echo ----------------------------------------------------------------------------------\n
echo \n