Thread: debugging in pgadmin
Hi all
A lot of time since the last debugging activity.
I don't remember how to debug. I thought I had to set a breaking point in the function i want to debug,
and then call that function.
I'm doing this, and from another query window, i call the function. But it returns me the result, but it doesn't stop inside the function in order to debug it.
What am i doing wrong?
thx
Josep
A lot of time since the last debugging activity.
I don't remember how to debug. I thought I had to set a breaking point in the function i want to debug,
and then call that function.
I'm doing this, and from another query window, i call the function. But it returns me the result, but it doesn't stop inside the function in order to debug it.
What am i doing wrong?
thx
Josep
--- On Mon, 23/3/09, josep porres <jmporres@gmail.com> wrote: > A lot of time since the last debugging activity. > I don't remember how to debug. I thought I had to set a > breaking point in > the function i want to debug, > and then call that function. > I'm doing this, and from another query window, i call > the function. But it > returns me the result, but it doesn't stop inside the > function in order to > debug it. > What am i doing wrong? Perhaps you've not got the pldebugger contrib module installed and run the sql script to create the debug functions?
mmm... my database schema have the pldbg functions.
2009/3/23 Glyn Astill <glynastill@yahoo.co.uk>
Perhaps you've not got the pldebugger contrib module installed and run the sql script to create the debug functions?
--- On Mon, 23/3/09, josep porres <jmporres@gmail.com> wrote:
> A lot of time since the last debugging activity.
> I don't remember how to debug. I thought I had to set a
> breaking point in
> the function i want to debug,
> and then call that function.
> I'm doing this, and from another query window, i call
> the function. But it
> returns me the result, but it doesn't stop inside the
> function in order to
> debug it.
> What am i doing wrong?
On Mon, Mar 23, 2009 at 12:40 PM, josep porres <jmporres@gmail.com> wrote: > mmm... my database schema have the pldbg functions. Do you have something like this in your postgresql.conf: shared_preload_libraries = '$libdir/plugins/plugin_debugger.so' ? If not, add it, and restart the server (if you're on Windows, use plugin_debugger.dll) -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
yes, i have:
shared_preload_libraries = '$libdir/plugins/plugin_debugger.dll' # (change requires restart)
shared_preload_libraries = '$libdir/plugins/plugin_debugger.dll' # (change requires restart)
2009/3/23 Dave Page <dpage@pgadmin.org>
On Mon, Mar 23, 2009 at 12:40 PM, josep porres <jmporres@gmail.com> wrote:Do you have something like this in your postgresql.conf:
> mmm... my database schema have the pldbg functions.
shared_preload_libraries = '$libdir/plugins/plugin_debugger.so'
?
If not, add it, and restart the server (if you're on Windows, use
plugin_debugger.dll)
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
it is Postgres Plus 8.3
Postgres 8.3.4 build 1400
Postgres 8.3.4 build 1400
2009/3/23 josep porres <jmporres@gmail.com>
yes, i have:
shared_preload_libraries = '$libdir/plugins/plugin_debugger.dll' # (change requires restart)2009/3/23 Dave Page <dpage@pgadmin.org>On Mon, Mar 23, 2009 at 12:40 PM, josep porres <jmporres@gmail.com> wrote:Do you have something like this in your postgresql.conf:
> mmm... my database schema have the pldbg functions.
shared_preload_libraries = '$libdir/plugins/plugin_debugger.so'
?
If not, add it, and restart the server (if you're on Windows, use
plugin_debugger.dll)
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
On Mon, Mar 23, 2009 at 12:50 PM, josep porres <jmporres@gmail.com> wrote: > yes, i have: > shared_preload_libraries = '$libdir/plugins/plugin_debugger.dll' # > (change requires restart) Whats the output from: select * from pldbg_get_proxy_info(); -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
"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
"PostgreSQL 8.3devel on i686-pc-mingw32, compiled by GCC gcc.exe (GCC) 3.4.2 (mingw-special)",80300,3,4220
2009/3/23 Dave Page <dpage@pgadmin.org>
On Mon, Mar 23, 2009 at 12:50 PM, josep porres <jmporres@gmail.com> wrote:Whats the output from:
> yes, i have:
> shared_preload_libraries = '$libdir/plugins/plugin_debugger.dll' #
> (change requires restart)
select * from pldbg_get_proxy_info();
--
On Mon, Mar 23, 2009 at 1:07 PM, josep porres <jmporres@gmail.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
that way I can debug =)
i attach the pgadmin.log zipped
i attach the pgadmin.log zipped
2009/3/23 Dave Page <dpage@pgadmin.org>
On Mon, Mar 23, 2009 at 1:07 PM, josep porres <jmporres@gmail.com> wrote:That should work, despite the mismatch in build envs (ignore the devel
> "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
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?
--
Attachment
On Mon, Mar 23, 2009 at 1:41 PM, josep porres <jmporres@gmail.com> wrote: > that way I can debug =) OK, so in that case can I get a log of an attempt to set a global breakpoint please? -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
in the previous action, first of all I made a breakpoint and called the function from a query window.
nothing happened, the only thing i got: the result.
All actions are in the previous log.
Is it what you want?
nothing happened, the only thing i got: the result.
All actions are in the previous log.
Is it what you want?
2009/3/23 Dave Page <dpage@pgadmin.org>
OK, so in that case can I get a log of an attempt to set a global
breakpoint please?
--
well, now a log with only trying to debug setting a breakpoint
2009/3/23 josep porres <jmporres@gmail.com>
in the previous action, first of all I made a breakpoint and called the function from a query window.
nothing happened, the only thing i got: the result.
All actions are in the previous log.
Is it what you want?2009/3/23 Dave Page <dpage@pgadmin.org>On Mon, Mar 23, 2009 at 1:41 PM, josep porres <jmporres@gmail.com> wrote:
> that way I can debug =)OK, so in that case can I get a log of an attempt to set a global
breakpoint please?
--
Attachment
On Mon, Mar 23, 2009 at 1:56 PM, josep porres <jmporres@gmail.com> wrote: > well, now a log with only trying to debug setting a breakpoint Hmmm - do you still have the demo schema on that server? Can you try setting a breakpoint on the list_emp() function, and then calling it please? -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
good morning,
I have a demo database, but it's empty.
if you tell me where is the creation script, I will try it
I have a demo database, but it's empty.
if you tell me where is the creation script, I will try it
2009/3/23 Dave Page <dpage@pgadmin.org>
On Mon, Mar 23, 2009 at 1:56 PM, josep porres <jmporres@gmail.com> wrote:Hmmm - do you still have the demo schema on that server? Can you try
> well, now a log with only trying to debug setting a breakpoint
setting a breakpoint on the list_emp() function, and then calling it
Ooops, I haven't realized the second schema, I've found the function.
Here you are your test log.
Here you are your test log.
2009/3/24 josep porres <jmporres@gmail.com>
good morning,
I have a demo database, but it's empty.
if you tell me where is the creation script, I will try it2009/3/23 Dave Page <dpage@pgadmin.org>On Mon, Mar 23, 2009 at 1:56 PM, josep porres <jmporres@gmail.com> wrote:
> well, now a log with only trying to debug setting a breakpointHmmm - do you still have the demo schema on that server? Can you try
setting a breakpoint on the list_emp() function, and then calling it
Attachment
On Tue, Mar 24, 2009 at 7:50 AM, josep porres <jmporres@gmail.com> wrote: > Ooops, I haven't realized the second schema, I've found the function. > Here you are your test log. OK, I think we've tracked down the problem. Can I send you some updated DLLs to try offlist? -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
i've just upgraded the server to 8.3.7 holding the same data directory
select * from pldbg_get_proxy_info();
"serverversionstr","serverversionnum","proxyapiver","serverprocessid"
"PostgreSQL 8.3devel on i686-pc-mingw32, compiled by GCC gcc.exe (GCC) 3.4.2 (mingw-special)",80300,3,2948
is it ok for testing your dll's?
select * from pldbg_get_proxy_info();
"serverversionstr","serverversionnum","proxyapiver","serverprocessid"
"PostgreSQL 8.3devel on i686-pc-mingw32, compiled by GCC gcc.exe (GCC) 3.4.2 (mingw-special)",80300,3,2948
is it ok for testing your dll's?
2009/3/24 Dave Page <dpage@pgadmin.org>
On Tue, Mar 24, 2009 at 7:50 AM, josep porres <jmporres@gmail.com> wrote:OK, I think we've tracked down the problem. Can I send you some
> Ooops, I haven't realized the second schema, I've found the function.
> Here you are your test log.
updated DLLs to try offlist?
--
by the way, after upgrading, i get the same behaviour
even executing the function in a query window created after setting the breakpoint.
even executing the function in a query window created after setting the breakpoint.
2009/3/24 josep porres <jmporres@gmail.com>
i've just upgraded the server to 8.3.7 holding the same data directory"serverversionstr","serverversionnum","proxyapiver","serverprocessid"
select * from pldbg_get_proxy_info();
"PostgreSQL 8.3devel on i686-pc-mingw32, compiled by GCC gcc.exe (GCC) 3.4.2 (mingw-special)",80300,3,2948
is it ok for testing your dll's?2009/3/24 Dave Page <dpage@pgadmin.org>On Tue, Mar 24, 2009 at 7:50 AM, josep porres <jmporres@gmail.com> wrote:OK, I think we've tracked down the problem. Can I send you some
> Ooops, I haven't realized the second schema, I've found the function.
> Here you are your test log.
updated DLLs to try offlist?
--
On Tue, Mar 24, 2009 at 1:42 PM, josep porres <jmporres@gmail.com> wrote: > i've just upgraded the server to 8.3.7 holding the same data directory > > select * from pldbg_get_proxy_info(); > "serverversionstr","serverversionnum","proxyapiver","serverprocessid" > "PostgreSQL 8.3devel on i686-pc-mingw32, compiled by GCC gcc.exe (GCC) 3.4.2 > (mingw-special)",80300,3,2948 > > is it ok for testing your dll's? Yes. I'll sent them offlist if that's OK? -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
asdfasdfasdfasdfasdfasdfasdfasdfasdfasd asdfasdffffffffffffffffffffffffffffffffffffffffffffff asdfasdfasdfasdfasdfasdfasdfasdfasdfasd asdfasdffffffffffffffffffffffffffffffffffffffffffffff asdfasdfasdfasdfasdfasdfasdfasdfasdfasd asdfasdffffffffffffffffffffffffffffffffffffffffffffff asdfasdfasdfasdfasdfasdfasdfasdfasdfasd asdfasdffffffffffffffffffffffffffffffffffffffffffffff asdfasdfasdfasdfasdfasdfasdfasdfasdfasd asdfasdffffffffffffffffffffffffffffffffffffffffffffff asdfasdfasdfasdfasdfasdfasdfasdfasdfasd asdfasdffffffffffffffffffffffffffffffffffffffffffffff asdfasdfasdfasdfasdfasdfasdfasdfasdfasd asdfasdffffffffffffffffffffffffffffffffffffffffffffff asdfasdfasdfasdfasdfasdfasdfasdfasdfasd asdfasdffffffffffffffffffffffffffffffffffffffffffffff asdfasdfasdfasdfasdfasdfasdfasdfasdfasd asdfasdffffffffffffffffffffffffffffffffffffffffffffff asdfasdfasdfasdfasdfasdfasdfasdfasdfasd asdfasdffffffffffffffffffffffffffffffffffffffffffffff asdfasdfasdfasdfasdfasdfasdfasdfasdfasd asdfasdffffffffffffffffffffffffffffffffffffffffffffff asdfasdfasdfasdfasdfasdfasdfasdfasdfasd asdfasdffffffffffffffffffffffffffffffffffffffffffffff asdfasdfasdfasdfasdfasdfasdfasdfasdfasd asdfasdffffffffffffffffffffffffffffffffffffffffffffff asdfasdfasdfasdfasdfasdfasdfasdfasdfasd asdfasdffffffffffffffffffffffffffffffffffffffffffffff asdfasdfasdfasdfasdfasdfasdfasdfasdfasd asdfasdffffffffffffffffffffffffffffffffffffffffffffff asdfasdfasdfasdfasdfasdfasdfasdfasdfasd asdfasdffffffffffffffffffffffffffffffffffffffffffffff asdfasdfasdfasdfasdfasdfasdfasdfasdfasd asdfasdffffffffffffffffffffffffffffffffffffffffffffff asdfasdfasdfasdfasdfasdfasdfasdfasdfasd asdfasdffffffffffffffffffffffffffffffffffffffffffffff asdfasdfasdfasdfasdfasdfasdfasdfasdfasd asdfasdffffffffffffffffffffffffffffffffffffffffffffff asdfasdfasdfasdfasdfasdfasdfasdfasdfasd asdfasdffffffffffffffffffffffffffffffffffffffffffffff asdfasdfasdfasdfasdfasdfasdfasdfasdfasd asdfasdffffffffffffffffffffffffffffffffffffffffffffff asdfasdfasdfasdfasdfasdfasdfasdfasdfasd asdfasdffffffffffffffffffffffffffffffffffffffffffffff asdfasdfasdfasdfasdfasdfasdfasdfasdfasd asdfasdffffffffffffffffffffffffffffffffffffffffffffff asdfasdfasdfasdfasdfasdfasdfasdfasdfasd asdfasdffffffffffffffffffffffffffffffffffffffffffffff asdfasdfasdfasdfasdfasdfasdfasdfasdfasd asdfasdffffffffffffffffffffffffffffffffffffffffffffff asdfasdfasdfasdfasdfasdfasdfasdfasdfasd asdfasdffffffffffffffffffffffffffffffffffffffffffffff asdfasdfasdfasdfasdfasdfasdfasdfasdfasd asdfasdffffffffffffffffffffffffffffffffffffffffffffff asdfasdfasdfasdfasdfasdfasdfasdfasdfasd asdfasdffffffffffffffffffffffffffffffffffffffffffffff asdfasdfasdfasdfasdfasdfasdfasdfasdfasd asdfasdffffffffffffffffffffffffffffffffffffffffffffff asdfasdfasdfasdfasdfasdfasdfasdfasdfasd asdfasdffffffffffffffffffffffffffffffffffffffffffffff asdfasdfasdfasdfasdfasdfasdfasdfasdfasd asdfasdffffffffffffffffffffffffffffffffffffffffffffff asdfasdfasdfasdfasdfasdfasdfasdfasdfasd asdfasdffffffffffffffffffffffffffffffffffffffffffffff asdfasdfasdfasdfasdfasdfasdfasdfasdfasd asdfasdffffffffffffffffffffffffffffffffffffffffffffff asdfasdfasdfasdfasdfasdfasdfasdfasdfasd asdfasdffffffffffffffffffffffffffffffffffffffffffffff asdfasdfasdfasdfasdfasdfasdfasdfasdfasd asdfasdffffffffffffffffffffffffffffffffffffffffffffff asdfasdfasdfasdfasdfasdfasdfasdfasdfasd asdfasdffffffffffffffffffffffffffffffffffffffffffffff asdfasdfasdfasdfasdfasdfasdfasdfasdfasd asdfasdffffffffffffffffffffffffffffffffffffffffffffff asdfasdfasdfasdfasdfasdfasdfasdfasdfasd asdfasdffffffffffffffffffffffffffffffffffffffffffffff asdfasdfasdfasdfasdfasdfasdfasdfasdfasd asdfasdffffffffffffffffffffffffffffffffffffffffffffff asdfasdfasdfasdfasdfasdfasdfasdfasdfasd asdfasdffffffffffffffffffffffffffffffffffffffffffffff asdfasdfasdfasdfasdfasdfasdfasdfasdfasd asdfasdffffffffffffffffffffffffffffffffffffffffffffff josep porres escreveu: > Ooops, I haven't realized the second schema, I've found the function. > Here you are your test log. > > 2009/3/24 josep porres <jmporres@gmail.com <mailto:jmporres@gmail.com>> > > good morning, > > I have a demo database, but it's empty. > if you tell me where is the creation script, I will try it > > 2009/3/23 Dave Page <dpage@pgadmin.org <mailto:dpage@pgadmin.org>> > > On Mon, Mar 23, 2009 at 1:56 PM, josep porres > <jmporres@gmail.com <mailto:jmporres@gmail.com>> wrote: > > > well, now a log with only trying to debug setting a breakpoint > > Hmmm - do you still have the demo schema on that server? Can > you try > setting a breakpoint on the list_emp() function, and then > calling it > please? > > > -- > Dave Page > EnterpriseDB UK: http://www.enterprisedb.com > > > > ------------------------------------------------------------------------ > > > -- ----------------------------------------------------- Uberdam Cavaletti Formado em Tecnologia da informação - Unoesc - Xxe Pós graduado em Desenvolvimento Java - Unoesc - Xxe Acesse http://www.curricular.com.br/berdam Acesse http://passandoveneno.blogspot.com -----------------------------------------------------