X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 71169D1B89A for ; Thu, 30 Oct 2003 17:34:55 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 98499-08 for ; Thu, 30 Oct 2003 13:34:24 -0400 (AST) Received: from smtp101.mail.sc5.yahoo.com (smtp101.mail.sc5.yahoo.com [216.136.174.139]) by svr1.postgresql.org (Postfix) with SMTP id 3E574D1B53A for ; Thu, 30 Oct 2003 13:34:23 -0400 (AST) Received: from pcp01341166pcs.wilog301.pa.comcast.net (HELO europa.janwieck.net) (janwieck@68.80.245.191 with login) by smtp.mail.vip.sc5.yahoo.com with SMTP; 30 Oct 2003 17:34:22 -0000 Received: from Yahoo.com (ismtp.afilias.com [216.217.55.254]) (authenticated) by europa.janwieck.net (8.11.6/8.11.6) with ESMTP id h9UHYJ324291; Thu, 30 Oct 2003 12:34:19 -0500 Message-ID: <3FA14B78.4030904@Yahoo.com> Date: Thu, 30 Oct 2003 12:33:44 -0500 From: Jan Wieck User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tomasz Myrta Cc: Lista dyskusyjna pgsql-sql Subject: Re: strange postgresql failure References: <3FA0F6E9.5060404@klaster.net> <3FA103AF.1000006@klaster.net> In-Reply-To: <3FA103AF.1000006@klaster.net> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/403 X-Sequence-Number: 15803 Tomasz Myrta wrote: > Dnia 2003-10-30 12:32, Użytkownik Tomasz Myrta napisał: >> After few seconds all backends were disconnected and postgres restarted. >> It didn't help :-( Even reboot didn't help... >> >> Postgres is 7.3.2-2 on Debian Woody. > > Sorry for my panic. It was my C function which raised segmentation fault. > > Anyway it would be nice to have some human readable control over C > functions... There is, sort of ... it's called "core" and if your backend and C function shared object have been compiled with symbol information you can use a debugger to get a stack trace and look at variables. If that's not "human readable" ... well ... I suppose I'm not human. Jan -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #================================================== JanWieck@Yahoo.com #