X-Original-To: pgsql-interfaces-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 2C7549DCA93 for ; Mon, 6 Feb 2006 21:24:14 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 99001-10 for ; Mon, 6 Feb 2006 21:24:17 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from candle.pha.pa.us (candle.pha.pa.us [70.90.9.53]) by postgresql.org (Postfix) with ESMTP id BDCCF9DC9D7 for ; Mon, 6 Feb 2006 21:24:10 -0400 (AST) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.11.6) id k171OJ128183; Mon, 6 Feb 2006 20:24:19 -0500 (EST) From: Bruce Momjian Message-Id: <200602070124.k171OJ128183@candle.pha.pa.us> Subject: Re: PQprint under Windows In-Reply-To: <43E7DB7F.7030101@online.de> To: Christoph Zwerschke Date: Mon, 6 Feb 2006 20:24:19 -0500 (EST) CC: pgsql-interfaces@postgresql.org X-Mailer: ELM [version 2.4ME+ PL121 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.127 required=5 tests=[AWL=0.127] X-Spam-Score: 0.127 X-Spam-Level: X-Archive-Number: 200602/18 X-Sequence-Number: 5982 Christoph Zwerschke wrote: > Bruce Momjian wrote: > > Christoph Zwerschke wrote: > >> I tried to compile PyGreSQL under Windows. > >> Everything seems to work, except some functions which are using PQprint. > >> Whenever these functions are called, I get a Windows exception. > >> ... > >> Can anybody confirm that PQprint is or was ever running under Windows? > >> The 8.1 docu does not say that it is deprecated or not running under > >> Windows. Can it be a bug? > > > > It should work. What exception are you getting, and what line in the C > > file is it complaining about? > > Here is the exception I am getting: > ------------------------------------------------------------------- > pythonw.exe caused an Invalid Handle at location 7c974ed1 in module > ntdll.dll. > > Registers: > eax=0021f6a0 ebx=00000000 ecx=0021f6e8 edx=7c91eb94 esi=7c38b528 > edi=00000000 > eip=7c974ed1 esp=0021f6a0 ebp=0021f6f0 iopl=0 nv up ei pl zr na > po nc > cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 > efl=00000246 > > Call stack: > 7C974ED1 ntdll.dll:7C974ED1 RtlRaiseStatus > 7C95243C ntdll.dll:7C95243C RtlInitializeSListHead > 7C91104B ntdll.dll:7C91104B RtlEnterCriticalSection > 77C1174F msvcrt.dll:77C1174F fwrite > 6311321C libpq.dll:6311321C pg_encoding_to_char > 63114007 libpq.dll:63114007 pg_encoding_to_char > 63114067 libpq.dll:63114067 pg_encoding_to_char > 631094A2 libpq.dll:631094A2 PQprint > 10003DC3 _pg.dll:10003DC3 _onexit dllcrt1.c:183 > _onexit_t _onexit( > _onexit_t pfn = &0x00a7a110 > ------------------------------------------------------------------- > > This happened when I was using the libpq.dll from the official binary > distribution of PostgreSQL 8.1.2. When I compiled libpq.dll myself to > find out more, amazingly everything worked fine, there was no exception. > I compiled with nls enabled and without, both works. Only the dll which > comes with the Win installer causes the problem. Any ideas what could be > the problem here? Wow, that is strange. Guess we will just wait for someone else to see the failure if you can not reproduce it. Thanks for trying. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073