On Mon, Jul 11, 2011 at 12:56 PM, Tom Lane wrote:
> Gurjeet Singh writes:
> > The attached patch registers a signal handler for SIGSEGV and
> launches
> > GDB in batch mode on its own pid so that the stack leading to the SEGV
> can
> > be dumped in the server logs.
>
> Did you not read the t
Gurjeet Singh writes:
> The attached patch registers a signal handler for SIGSEGV and launches
> GDB in batch mode on its own pid so that the stack leading to the SEGV can
> be dumped in the server logs.
Did you not read the thread last week about how we did not want any such
thing?
Quite as
Hi,
The attached patch registers a signal handler for SIGSEGV and launches
GDB in batch mode on its own pid so that the stack leading to the SEGV can
be dumped in the server logs. Also attached is an example of the stack
dumped by gdb in server log file (caused by a `kill -segv nnn` on the
bac
