| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | josep porres <jmporres(at)gmail(dot)com> |
| Cc: | glynastill(at)yahoo(dot)co(dot)uk, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: debugging in pgadmin |
| Date: | 2009-03-23 13:27:41 |
| Message-ID: | 937d27e10903230627h50096501r2862aaad18b69183@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Mar 23, 2009 at 1:07 PM, josep porres <jmporres(at)gmail(dot)com> wrote:
> "serverversionstr","serverversionnum","proxyapiver","serverprocessid"
> "PostgreSQL 8.3devel on i686-pc-mingw32, compiled by GCC gcc.exe (GCC) 3.4.2
> (mingw-special)",80300,3,4220
That should work, despite the mismatch in build envs (ignore the devel
bit - that just tells us what version of Postgres the plugin was
compiled against).
What happens if you right-click a function in pgAdmin and select the
Debug option (not the Set Breakpoint option)? If that doesn't work,
can you please set the pgAdmin log level to debug, retry the test and
then send the log over?
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | josep porres | 2009-03-23 13:41:35 | Re: debugging in pgadmin |
| Previous Message | josep porres | 2009-03-23 13:07:40 | Re: debugging in pgadmin |