Changes between Version 8 and Version 9 of DevWikiGettingABackTrace

Timestamp:

Dec 12, 2021, 8:58:13 AM (2 years ago)

Author:

gdt

Comment:

—

DevWikiGettingABackTrace

@@ -155 +155 @@
 = Using with regression tests =
 
-Sometimes there is a crash during regression tests.
+Sometimes there is a crash during regression tests, and it's useful to get a backtrace
+
+== Safer Instructions ==
+
+These instructions are likely better and safer.
+
+  * make staged-install # from top-level
+  * regress/run_test.pl --nodrop regress/core/geography.sql
+  * psql postgis_reg
+  * select pg_backend_pid();
+  * attach gdb to backend
+  * psql> \i regress/core/geography.sql
+
+== Simpler, perhpas less reliable approach ==
 
 When running "make test", a number of things happen, including creating some test files and creating the "postgis_reg" database and loading the working tree postgis into it.  Then, tests are run.  It would be difficult to replicate all of this in a script to run gdb.
 
-Instead, the recommended approach is to first run "make test", to cause all the setup to happen.   Then, identify the first failing test, as debugging anything after the first failure is far less likely to be useful.   Connect as "psql -d postgis_reg", and get the pid and attach gdb as above.
+Instead, one can first run "make test", to cause all the setup to happen.   While the database is normally dropped, it is (usually?) left on failure. Then, identify the first failing test, as debugging anything after the first failure is far less likely to be useful.   Connect as "psql -d postgis_reg", and get the pid and attach gdb as above.
 
 Then, e.g.