pgadmin debug on windows
in [PgSql]
|
Prev: rolcanlogin vs. the flat password file
Next: xlogdump
From: "Roberto Icardi" on 22 Oct 2007 09:26 Hello, I've installed on a windows xp machine beta 1 of postgresql 8.3 and pgadmin III 1.8. I've loaded a backup of a database from a 8.2.5 machine, for testing purpose, and tried the new functionality of plpgsql debug of functions. But I was disappointed to see that does not work. I try to debug right clicking on a function (very basic function indeed) and choosing debug->debug from the contextual menu, but what I obtain is "an unhandled exception occurred." and Abort/Retry/Ignore buttons. Same if I try to set breakpoint (i can see the debug window this way, but completely empty) Sorry I cannot give more details, but I don't have them myself <g> Can someone give me an idea of what's wrong? Is maybe debugging not yet available in this beta release of postgresql on windows??? Or the problem is that the function is imported from a 8.2.5 database? Thanks everyone.
From: Dave Page on 22 Oct 2007 09:38 Roberto Icardi wrote: > Hello, > > I've installed on a windows xp machine beta 1 of postgresql 8.3 and > pgadmin III 1.8. > I've loaded a backup of a database from a 8.2.5 machine, for testing > purpose, and tried > the new functionality of plpgsql debug of functions. > > But I was disappointed to see that does not work. > I try to debug right clicking on a function (very basic function indeed) > and choosing debug->debug from the contextual menu, but what I obtain is > "an unhandled exception occurred." and Abort/Retry/Ignore buttons. Same > if I try to set breakpoint > (i can see the debug window this way, but completely empty) > Sorry I cannot give more details, but I don't have them myself <g> > > Can someone give me an idea of what's wrong? Is maybe debugging not yet > available in this beta release > of postgresql on windows??? Or the problem is that the function is > imported from a 8.2.5 database? It works fine in all the extensive testing I've done on PostgreSQL 8.2 and 8.3, not to mention EnterpriseDB 8.1 and 8.2 - otherwise we wouldn't have released pgAdmin today. Can you post the source for your function, or a simple version with with you can recreate the problem? Regards, Dave ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend
From: "Roberto Icardi" on 22 Oct 2007 09:56 Dave, the problem isn't with a particular function. Debug does not work with every function I try, even with the simplest one, always with the same behaviour I've previously explained. I repeat, my postgresql server is an 8.3 beta 1 installed on the same machine where pgadmin III 1.8 is installed, a Windows XP SP2 machine. If you need more details, let me know............
From: Dave Page on 22 Oct 2007 10:09 Roberto Icardi wrote: > Dave, > > the problem isn't with a particular function. Debug does not work with > every function I try, even with the simplest one, always with the same > behaviour I've previously explained. > I repeat, my postgresql server is an 8.3 beta 1 installed on the same > machine where pgadmin III 1.8 is installed, a Windows XP SP2 machine. > > If you need more details, let me know............ Well it works with 8.3 beta 1 on every function I've tried here (on XP SP2) - that was one of my tests when I built the release, plus I've just tested again to be sure. Are the debugger functions *all* loaded in the database you're trying to debug? there should be: pldbg_abort_target(integer) pldbg_attach_to_port(integer) pldbg_continue(integer) pldbg_create_listener() pldbg_deposit_value(integer, text, integer, text) pldbg_drop_breakpoint(integer, oid, integer) pldbg_get_breakpoints(integer) pldbg_get_proxy_info() pldbg_get_source(integer, oid) pldbg_get_stack(integer) pldbg_get_target_info(text, "char") pldbg_get_variables(integer) pldbg_select_frame(integer, integer) pldbg_set_breakpoint(integer, oid, integer) pldbg_set_global_breakpoint(integer, oid, integer, integer) pldbg_step_into(integer) pldbg_step_over(integer) pldbg_wait_for_breakpoint(integer) pldbg_wait_for_target(integer) plpgsql_oid_debug(oid) Regards, Dave ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to majordomo(a)postgresql.org so that your message can get through to the mailing list cleanly
From: "Roberto Icardi" on 22 Oct 2007 10:15
Yes, they are all there.... I've also tried on a newly created database instead of testing on a restored from 8.2. backup but with the same behaviour :-( ----- Original Message ----- From: "Dave Page" <dpage(a)postgresql.org> To: "Roberto Icardi" <roberto_icardi(a)hotmail.com> Cc: <pgsql-hackers(a)postgresql.org> Sent: Monday, October 22, 2007 4:09 PM Subject: Re: [HACKERS] pgadmin debug on windows > Roberto Icardi wrote: >> Dave, >> >> the problem isn't with a particular function. Debug does not work with >> every function I try, even with the simplest one, always with the same >> behaviour I've previously explained. >> I repeat, my postgresql server is an 8.3 beta 1 installed on the same >> machine where pgadmin III 1.8 is installed, a Windows XP SP2 machine. >> >> If you need more details, let me know............ > > Well it works with 8.3 beta 1 on every function I've tried here (on XP > SP2) - that was one of my tests when I built the release, plus I've just > tested again to be sure. > > Are the debugger functions *all* loaded in the database you're trying to > debug? there should be: > > pldbg_abort_target(integer) > pldbg_attach_to_port(integer) > pldbg_continue(integer) > pldbg_create_listener() > pldbg_deposit_value(integer, text, integer, text) > pldbg_drop_breakpoint(integer, oid, integer) > pldbg_get_breakpoints(integer) > pldbg_get_proxy_info() > pldbg_get_source(integer, oid) > pldbg_get_stack(integer) > pldbg_get_target_info(text, "char") > pldbg_get_variables(integer) > pldbg_select_frame(integer, integer) > pldbg_set_breakpoint(integer, oid, integer) > pldbg_set_global_breakpoint(integer, oid, integer, integer) > pldbg_step_into(integer) > pldbg_step_over(integer) > pldbg_wait_for_breakpoint(integer) > pldbg_wait_for_target(integer) > plpgsql_oid_debug(oid) > > Regards, Dave > > > ---------------------------(end of broadcast)--------------------------- TIP 5: don't forget to increase your free space map settings |