Re: Perl 5.10 vs. PG 8.4 on Win32 - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Perl 5.10 vs. PG 8.4 on Win32
Date
Msg-id 13037.1242424508@sss.pgh.pa.us
Whole thread Raw
In response to Re: Perl 5.10 vs. PG 8.4 on Win32  (Dave Page <dpage@pgadmin.org>)
Responses Re: Perl 5.10 vs. PG 8.4 on Win32
List pgsql-bugs
Dave Page <dpage@pgadmin.org> writes:
> I've been playing with this for the last couple of hours, to no avail.
> Looking at the log with PIDs, it certainly appears to be the crashing
> backend that calls the atexit callback. I can't get a backtrace though
> - if I attach the debugger before crashing, it breaks out at the
> exception and won't continue. If I add an infinite loop in
> atexit_callback to 'pause' the process I can attach and break, but for
> some reason the debugger doesn't recognise the loop control variable,
> so I can't modify the value to make it continue. That stops me even
> getting the server to complete startup :-(

This is a bit devious, but ... add an on_proc_exit call that's set up
by plperl.c's init before it calls Perl, and put the infinite loop
inside there.  Then you don't hit it in any of the other processes.

            regards, tom lane

pgsql-bugs by date:

Previous
From: Dave Page
Date:
Subject: Re: Perl 5.10 vs. PG 8.4 on Win32
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] Re: BUG #4796: Recovery followed by backup creates unrecoverable WAL-file