| From: | "Florian G(dot) Pflug" <fgp(at)phlo(dot)org> |
|---|---|
| To: | "A(dot)M(dot)" <agentm(at)themactionfaction(dot)com> |
| Cc: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: GUI Interface |
| Date: | 2006-05-18 20:05:28 |
| Message-ID: | 446CD388.20309@phlo.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
A.M. wrote:
> Excellent catch! I was wondering why I couldn't get it to freeze. I now
> have a backtrace:
> poll()
> wxPaletteBase::~wxPaletteBase
> g_main_context_check()
> g_main_run_loop_run()
> gtk_main()
> wxEventLoop::Run()
>
> So the evidence points to a wx bug in the destructor to wxPaletteBase
> perhaps?
Hm.. all very strange...
I just build wxGTK 2.6.3 and pgadmin3 1.4.2 using g++ 3.3 on Ubuntu
Dapper, and _the_bug_is_gone_!.
When I double-click a selection using my self-compiled version, the
text is just unselected.
Doing the same in the version that I compiled by fetching the
source-package from debian/etch, and doing "dpkg-buildpackage -us -uc
-b" freezes X.
I'm going to compare wx configure flags now...
BTW, I used g++ 3.3 because a build using g++ 4.0 would crash instantly
when started (without showing even the tiniest bit of GUI...)
greetings, Florian
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Florian G. Pflug | 2006-05-18 20:15:15 | Re: GUI Interface |
| Previous Message | Kenneth Downs | 2006-05-18 19:43:10 | Re: GUI Interface |