| From: | Peter Geoghegan <peter(at)2ndquadrant(dot)com> |
|---|---|
| To: | Dave Page <dpage(at)pgadmin(dot)org> |
| Cc: | Aleksey Chirkin <a4irkin(at)gmail(dot)com>, pgadmin-support(at)postgresql(dot)org |
| Subject: | Re: SQL Editor fail |
| Date: | 2011-05-12 15:42:27 |
| Message-ID: | BANLkTi=hqQW-kTGXbuiXQggkQj6xXHTbHA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
On 12 May 2011 16:15, Dave Page <dpage(at)pgadmin(dot)org> wrote:
> Hmm, I can reproduce it, but I have no idea what the problem is. The
> stack trace (which contains 56977 frames!!) indicates the crash
> happens deep in Apples rendering code, which in turn is called from
> wxWidgets painting code which is called by the main event loop. As far
> as I can see, there is no pgAdmin code in the stack at all.
Yeah, I tend to see that a lot with GUI code, where events are handled
asynchronously. Often, the trick is to carpetbomb a whole bunch of
breakpoints haphazardly in the general area of the problem, and then
when triggering the problem, as each breakpoint is hit, disable them
one-by-one, until you see the error again, at which point you
re-enable the most recently disabled breakpoint. You are now near to
the problem.
Sorry if that's obvious - I can't really tell.
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Belbin, Peter | 2011-05-12 16:41:37 | Re: Usability improvment ideas |
| Previous Message | Dave Page | 2011-05-12 15:15:11 | Re: SQL Editor fail |