| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | elog a stack trace |
| Date: | 2014-05-02 15:16:39 |
| Message-ID: | CAMkU=1wCVL53o+ye-bX8UO41gPJESimNJGGvbc1u7qqe3VXOOw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Does anyone have any hints on how to get a stack trace programmatically,
rather than trying to run ps to get the pid and then attach gdb to a
ephemeral process and hoping the situation has not been changed while you
are doing that? I'd like to set
log_error_verbosity = stack
or
elog_stack(,...)
But those don't exist.
Cheers,
Jeff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2014-05-02 15:18:35 | Re: elog a stack trace |
| Previous Message | Andres Freund | 2014-05-02 15:04:01 | Sending out a request for more buildfarm animals? |