| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | more backtraces |
| Date: | 2019-12-04 19:45:25 |
| Message-ID: | 73851414-b985-455c-249d-dcdf33551891@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
In the previous discussions on backtrace support, some people asked for
backtraces in more situations. Here is a patch that prints backtraces
on SIGABRT, SIGBUS, and SIGSEGV signals. SIGABRT includes assertions
and elog(PANIC).
Do signals work like this on Windows? Do we need special EXEC_BACKEND
support?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Print-backtrace-on-SIGABRT-SIGBUS-SIGSEGV.patch | text/plain | 3.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2019-12-04 19:59:15 | Re: more backtraces |
| Previous Message | Andres Freund | 2019-12-04 19:43:32 | Re: Why JIT speed improvement is so modest? |