> On 5 Dec 2019, at 00:45, Peter Eisentraut
> wrote:
>
> <0001-Print-backtrace-on-SIGABRT-SIGBUS-SIGSEGV.patch>
Hello!
I find this patch very useful when hacking, so let's have a rebased version in
archives.
And +1 for the feature. The backtrace could help collect diagnostics in case of
p
On 2019-Dec-15, Tom Lane wrote:
> Robert Haas writes:
> > Being able to get debugging information from
> > failures that happen on those installations that enables us to fix
> > things without having to go through a time-consuming process of
> > guesswork and attempted reproduction is really valu
Robert Haas writes:
> On Fri, Dec 13, 2019 at 7:26 AM Peter Eisentraut
>> Are people interested in backtraces on abort()? That was asked for in
>> an earlier thread.
FWIW, I don't have too much of an opinion about abort() yet.
Aren't we covering most of the possible cases for that already?
I don
On Fri, Dec 13, 2019 at 7:26 AM Peter Eisentraut
wrote:
> On 2019-12-04 22:34, Tom Lane wrote:
> > Andres Freund writes:
> >> It'd be bad if the addition of backtraces for SEGV/BUS suddenly made it
> >> harder to attach a debugger and getting useful results.
> >
> > Yeah. TBH, I'm not sure I wan
On 2019-12-04 22:34, Tom Lane wrote:
Andres Freund writes:
It'd be bad if the addition of backtraces for SEGV/BUS suddenly made it
harder to attach a debugger and getting useful results.
Yeah. TBH, I'm not sure I want this, at least not in debug builds.
I understand that the SEGV/BUS thing
Andres Freund writes:
> It'd be bad if the addition of backtraces for SEGV/BUS suddenly made it
> harder to attach a debugger and getting useful results.
Yeah. TBH, I'm not sure I want this, at least not in debug builds.
regards, tom lane
On 2019-12-04 20:59, Andres Freund wrote:
On 2019-12-04 20:45:25 +0100, Peter Eisentraut wrote:
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 include
Hi,
On 2019-12-04 20:45:25 +0100, Peter Eisentraut wrote:
> 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).
H
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_B
