Received: from localhost (maia-1.hub.org [200.46.204.191])
	by postgresql.org (Postfix) with ESMTP id 59ACC9FA249
	for <pgsql-interfaces-postgresql.org@postgresql.org>;
	Tue,  2 Jan 2007 21:22:31 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.191]) (amavisd-new, port 10024)
	with ESMTP id 83615-08 for
	<pgsql-interfaces-postgresql.org@postgresql.org>;
	Tue,  2 Jan 2007 21:22:23 -0400 (AST)
X-Greylist: delayed 23:34:10.135578 by SQLgrey-1.7.4
Received: from elasmtp-junco.atl.sa.earthlink.net
	(elasmtp-junco.atl.sa.earthlink.net [209.86.89.63])
	by postgresql.org (Postfix) with ESMTP id BEFF29F95E3
	for <pgsql-interfaces@postgresql.org>;
	Tue,  2 Jan 2007 21:22:23 -0400 (AST)
Received: from [4.238.215.194] (helo=mindspring.com)
	by elasmtp-junco.atl.sa.earthlink.net with asmtp (TLSv1:AES256-SHA:256)
	(Exim 4.34) id 1H1upe-0000Gv-RC
	for pgsql-interfaces@postgresql.org; Tue, 02 Jan 2007 20:22:22 -0500
Received: (from lbayuk@localhost)
	by mindspring.com (8.13.7/8.13.7) id l031MWK9000395
	for pgsql-interfaces@postgresql.org; Tue, 2 Jan 2007 20:22:32 -0500
Date: Tue, 2 Jan 2007 20:22:32 -0500
From: L Bayuk <lbayuk@pobox.com>
To: pgsql-interfaces@postgresql.org
Subject: BCC-built psql does not work
Message-ID: <20070103012232.GA389@mail.mindspring.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.2.2i
X-ELNK-Trace: 
 7a0205cf9d42df0a5e89bb4777695beb69025943178dce0b5c2be9e490bcf0cf006ac59e07e9732e350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 4.238.215.194
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=0.068 tagged_above=0 required=5 tests=AWL, BAYES_50,
	FORGED_RCVD_HELO
X-Spam-Level: 
X-Archive-Number: 200701/4
X-Sequence-Number: 6382

On Mon, Jan 01, 2007 at 09:50:18PM +0000, Mark Morgan Lloyd wrote:
> 
> Do you find the resulting psql reliable? I got it built for 8.1
> but found it very flaky and ended up doing that sort of work
> using an ssh session to the (Linux) server.

I worked some more with BCC-built psql (PostgreSQL 8.2.0). Yes,
it is very broken. One way I can get it to crash is just by
repeating "\h set" 6 times. That's right, 5 times OK, 6th crashes.

I eventually figured out how to get a stack back-trace, of sorts, but I
don't know if it is reliable.  It seems to indicate the crash is in
psql_scan_finish(), calling yy_delete_buffer(), calling yy_flex_free().
But if I take that part out, it crashes somewhere else.  My best guess is
that it scribbled on memory and messed up the malloc/free heap areas.
Since I don't know any good way to debug this on Windows, and I don't
really need BCC-built psql anyway, I am probably going to just drop it.
All I need is libpq, and that seems fine with BCC.