Skip site navigation (1) Skip section navigation (2)

Re: Perl 5.10 vs. PG 8.4 on Win32

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Dave Page <dpage(at)pgadmin(dot)org>
Cc: Pg Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Perl 5.10 vs. PG 8.4 on Win32
Date: 2009-05-15 21:55:08
Message-ID: 13037.1242424508@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Dave Page <dpage(at)pgadmin(dot)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

In response to

Responses

pgsql-bugs by date

Next:From: George SuDate: 2009-05-15 21:57:39
Subject: BUG #4812: statistics not available on tables containing only hstore column
Previous:From: Dave PageDate: 2009-05-15 21:36:16
Subject: Re: Perl 5.10 vs. PG 8.4 on Win32

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group