Re: Old problem reoccurrence in current

From: Wahlstedt Jyrki <jwa(at)wahlstedt(dot)fi>
To: Dave Page <dpage(at)pgadmin(dot)org>
Cc: Wahlstedt Jyrki <jwa(at)wahlstedt(dot)fi>, pgadmin-hackers pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: Old problem reoccurrence in current
Date: 2012-08-30 20:44:46
Message-ID: 7DEB2CD2-42C7-4FC0-9EE8-E248BF2B1849@wahlstedt.fi
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers


On 29.8.2012, at 14.26, Dave Page <dpage(at)pgadmin(dot)org> wrote:

> On Tue, Aug 28, 2012 at 9:05 PM, Wahlstedt Jyrki <jwa(at)wahlstedt(dot)fi> wrote:
> Dear all,
> in March I experienced a reproducible crashing problem in pgAdmin3 (doubleclick on a table name on right-hand side pane). This is something I see again, now in an app built from a fresh git pull (configure says 1.17.0-dev). Now the message box gives a lot more information:
>
> I can't reproduce this here. Can you give any more info about what you're doing (server version, and specific steps etc).
>
>
> <PastedGraphic-1.png>

Hi,
so: I'm on OS X 10.8.1, with server version 9.1.5, used locally (i.e. localhost), built locally (via MacPorts). The steps being (after launch and connect to server): 1) connect to my database (i.e. the one with my name on it) 2) open schemas->public by triangles 3) when the schemas->public is open showing below it collations &c, click 'Tables' there, just the name, do not use the triangle 4) now the table names are shown on the right-hand side 5) double-click a table name (this invariably gives me a crash)

PS The crash info says 1.16.0-beta2

!
! Jyrki Wahlstedt
! http://www.wahlstedt.fi/jyrki/
!
! Our life is no dream; but it ought to become one and perhaps will.
! PGP key ID: 0x139CC386 fingerprint: F355 B46F 026C B8C1 89C0 A780 6366 EFD9 139C C386

In response to

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Dave Page 2012-08-31 15:47:26 Re: Old problem reoccurrence in current
Previous Message Dave Page 2012-08-29 11:26:52 Re: Old problem reoccurrence in current