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 4D2039DC866 for ; Mon, 6 Feb 2006 19:28:03 -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 72582-06 for ; Mon, 6 Feb 2006 19:28:05 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) by postgresql.org (Postfix) with ESMTP id 724129DC8DB for ; Mon, 6 Feb 2006 19:28:00 -0400 (AST) Received: from [84.173.61.210] (helo=[192.168.1.10]) by mrelayeu.kundenserver.de (node=mrelayeu6) with ESMTP (Nemesis), id 0ML29c-1F6Fm349k8-0004GJ; Tue, 07 Feb 2006 00:28:00 +0100 Message-ID: <43E7DB7F.7030101@online.de> Date: Tue, 07 Feb 2006 00:27:59 +0100 From: Christoph Zwerschke User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041206 Thunderbird/1.0 Mnenhy/0.6.0.104 MIME-Version: 1.0 To: pgsql-interfaces@postgresql.org Subject: Re: PQprint under Windows References: <200602060223.k162NLQ09958@candle.pha.pa.us> In-Reply-To: <200602060223.k162NLQ09958@candle.pha.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: kundenserver.de abuse@kundenserver.de login:d4c19f41f9a9703255691874c1441822 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.08 required=5 tests=[AWL=0.080] X-Spam-Score: 0.08 X-Spam-Level: X-Archive-Number: 200602/15 X-Sequence-Number: 5979 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? >> I also noticed that the HTML code in PQprint is not very clean and >> sometimes even wrong, e.g. it has instead of
. > > Fixed in 8.1.X. As already mentioned, there is also a wrong attribute align=high and as I just saw, also align=left and align=right attributes without quotes. -- Christoph