Skip site navigation (1) Skip section navigation (2)

Re: pgadmin crash on refresh

From: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Dave Page <dpage(at)pgadmin(dot)org>, pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: pgadmin crash on refresh
Date: 2011-01-22 00:19:11
Message-ID: (view raw or whole thread)
Lists: pgadmin-hackers
Le 21/01/2011 19:36, Magnus Hagander a écrit :
> On Fri, Jan 21, 2011 at 13:35, Dave Page <dpage(at)pgadmin(dot)org> wrote:
>> On Fri, Jan 21, 2011 at 12:20 PM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>>> On Wed, Jan 19, 2011 at 14:55, Dave Page <dpage(at)pgadmin(dot)org> wrote:
>>>> On Wed, Jan 19, 2011 at 12:18 PM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>>>>> Opened database->catalogs->pg_catalogs->tables. Right click + refresh = crash.
>>>>> Don't have time to dig in right now myself, but here's a backtrace if
>>>>> somebody wants to get started, or perhaps has a clue what it could
>>>>> be...
>>>>> this is with  current git master tip, debugging enabled.
>>>> Hmm, can't reproduce it on Windows. It does look an awful lot like
>>> Oh, additional point: you need to actually *expand* the tables node,
>>> or it doesn't crash. Did you by any chance not do that?
>> I did do that.
>>>> this though:;a=commit;h=9ec6b29fe3fbd9cc196d5e91b55f3697f02bcad8
>>> Nope. I reverted that patch (well, due to the style patch i couldn't,
>>> but i commented out that one line it seems to add) and it still
>>> crashes for me.
>> There's little chance that that patch would cause (or fix) the problem
>> you see - but a similar patch in a different place might be the fix.
> I've created ticket 299 for this for now, so we don't loose track of it.

Thanks Magnus.


In response to

pgadmin-hackers by date

Next:From: Guillaume LelargeDate: 2011-01-22 00:33:20
Subject: Re: Patch to support SSL certificate connections
Previous:From: Guillaume LelargeDate: 2011-01-22 00:18:19
Subject: Re: Number of selected characters.

Privacy Policy | About PostgreSQL
Copyright © 1996-2015 The PostgreSQL Global Development Group