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" <[EMAIL PROTECTED]>
To: "Roberto Icardi" <[EMAIL PROTECTED]>
Cc: <pgsql-hackers@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
