Tom Lane wrote:
> Stefan Kaltenbrunner <[EMAIL PROTECTED]> writes:
>> this patch definitly changes behaviour but not actually for the better :-(
>
> Oh well, it was worth a try. At this point I think we have to suppose
> this is a Tcl bug and not our fault. Can you reproduce the problem in
> bar
Alvaro Herrera wrote:
> Stefan Kaltenbrunner wrote:
>
>> backtrace for 7235:
>>
>> (gdb) bt
>
> Please do this in GDB:
>
> thread apply all bt
>
> (or maybe it is
> threads apply all bt)
>
> This'll give you backtraces for all threads in the process.
sorry forgot to mention that - the backtra
Stefan Kaltenbrunner <[EMAIL PROTECTED]> writes:
> this patch definitly changes behaviour but not actually for the better :-(
Oh well, it was worth a try. At this point I think we have to suppose
this is a Tcl bug and not our fault. Can you reproduce the problem in
bare "tclsh"? Try
$
Stefan Kaltenbrunner wrote:
> backtrace for 7235:
>
> (gdb) bt
Please do this in GDB:
thread apply all bt
(or maybe it is
threads apply all bt)
This'll give you backtraces for all threads in the process.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
PostgreS
Tom Lane wrote:
> I wrote:
>> One possibility for fixing it is that maybe we should be making an
>> effort to execute Tcl_Finalize() before exiting the backend. If so,
>> having pltcl set up an on_proc_exit callback to do it would be the
>> appropriate thing. This is all speculation though.
>
>
I wrote:
> One possibility for fixing it is that maybe we should be making an
> effort to execute Tcl_Finalize() before exiting the backend. If so,
> having pltcl set up an on_proc_exit callback to do it would be the
> appropriate thing. This is all speculation though.
Just for grins I tried thi
Stefan Kaltenbrunner <[EMAIL PROTECTED]> writes:
> FWIW - I removed --with-tcl from quagga's configuration about two weeks
> ago and it has not failed(for that reason) again. So the issue most
> definitly looks like plptcl related ...
I poked around a bit in the Tcl sources, and as far as I can te
Tom Lane wrote:
> Stefan Kaltenbrunner <[EMAIL PROTECTED]> writes:
>> FWIW - I removed --with-tcl from quagga's configuration about two weeks
>> ago and it has not failed(for that reason) again. So the issue most
>> definitly looks like plptcl related ...
>
> It sorta looks like Tcl might be insta
Stefan Kaltenbrunner <[EMAIL PROTECTED]> writes:
> FWIW - I removed --with-tcl from quagga's configuration about two weeks
> ago and it has not failed(for that reason) again. So the issue most
> definitly looks like plptcl related ...
It sorta looks like Tcl might be installing an atexit() callbac
Stefan Kaltenbrunner wrote:
> Tom Lane wrote:
>> Stefan Kaltenbrunner <[EMAIL PROTECTED]> writes:
>>> one of my new buildfarm boxes (an Debian/Etch based ARM box) is
>>> sometimes failing to stop the database during the regression tests:
>>> http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=qu
Tom Lane wrote:
> Stefan Kaltenbrunner <[EMAIL PROTECTED]> writes:
>> one of my new buildfarm boxes (an Debian/Etch based ARM box) is
>> sometimes failing to stop the database during the regression tests:
>
>> http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=quagga&dt=2007-01-08%2003:03:03
>
Stefan Kaltenbrunner <[EMAIL PROTECTED]> writes:
> one of my new buildfarm boxes (an Debian/Etch based ARM box) is
> sometimes failing to stop the database during the regression tests:
> http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=quagga&dt=2007-01-08%2003:03:03
> this only seems to ha
12 matches
Mail list logo
