| From: | josep porres <jmporres(at)gmail(dot)com> |
|---|---|
| To: | Dave Page <dpage(at)pgadmin(dot)org> |
| Cc: | glynastill(at)yahoo(dot)co(dot)uk, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: debugging in pgadmin |
| Date: | 2009-03-23 13:41:35 |
| Message-ID: | d2d532610903230641l630a6e6bo12b7a691104c1cdd@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
that way I can debug =)
i attach the pgadmin.log zipped
2009/3/23 Dave Page <dpage(at)pgadmin(dot)org>
> 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
>
| Attachment | Content-Type | Size |
|---|---|---|
| pgadmin.zip | application/zip | 7.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2009-03-23 13:48:23 | Re: debugging in pgadmin |
| Previous Message | Dave Page | 2009-03-23 13:27:41 | Re: debugging in pgadmin |