From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Thom Brown <thom(at)linux(dot)com> |
Cc: | pgadmin-support <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: [BUG] PgAdmin crashes after typing newline after open parenthesis |
Date: | 2011-06-27 14:33:04 |
Message-ID: | BANLkTima_wsdd42sH5qmGyzBCXX8sTHs=g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
On Mon, Jun 27, 2011 at 3:30 PM, Thom Brown <thom(at)linux(dot)com> wrote:
> On 25 June 2011 12:40, Thom Brown <thom(at)linux(dot)com> wrote:
>> Hi,
>>
>> I'm using PgAdmin III 1.14.0 beta 1 on 64-bit OSX 10.6.8, and whenever
>> I type an opening parenthesis in the SQL Editor and attempt to use a
>> newline it crashes the whole application. This happens regardless as
>> to whether the newline is immediately after opening, or has additional
>> text after it. I've tested the same thing on the current stable
>> version on Debian, and on a freshly compiled version from an
>> up-to-date Git clone, also on Debian, but can't recreate it.
>>
>> It looks like a segfault as I'm getting this in the crash report:
>>
>> Exception Type: EXC_BAD_ACCESS (SIGSEGV)
>> Exception Codes: KERN_PROTECTION_FAILURE at 0x00000000bf7ff4dc
>> Crashed Thread: 0 Dispatch queue: com.apple.main-thread
>>
>> I've also attached the stack trace.
>
> Anyone able to reproduce this?
That was fixed here:
http://git.postgresql.org/gitweb?p=pgadmin3.git;a=commitdiff;h=467e0d9072f15bb1d45a1374b5f713287d8d2a7c
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Thom Brown | 2011-06-27 14:38:49 | Re: [BUG] PgAdmin crashes after typing newline after open parenthesis |
Previous Message | Thom Brown | 2011-06-27 14:30:18 | Re: [BUG] PgAdmin crashes after typing newline after open parenthesis |