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 does
--- On Mon, 23/3/09, josep porres 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
mmm... my database schema have the pldbg functions.
2009/3/23 Glyn Astill
>
>
> --- On Mon, 23/3/09, josep porres 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,
>
On Mon, Mar 23, 2009 at 12:40 PM, josep porres 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,
yes, i have:
shared_preload_libraries = '$libdir/plugins/plugin_debugger.dll'#
(change requires restart)
2009/3/23 Dave Page
> On Mon, Mar 23, 2009 at 12:40 PM, josep porres wrote:
> > mmm... my database schema have the pldbg functions.
>
> Do you have something like this in your post
it is Postgres Plus 8.3
Postgres 8.3.4 build 1400
2009/3/23 josep porres
> yes, i have:
> shared_preload_libraries = '$libdir/plugins/plugin_debugger.dll'#
> (change requires restart)
>
>
> 2009/3/23 Dave Page
>
> On Mon, Mar 23, 2009 at 12:40 PM, josep porres wrote:
>> > mmm... my
On Mon, Mar 23, 2009 at 12:50 PM, josep porres 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
2009/3/23 Dave Page
> On Mon, Mar 23, 2009 at 12:50 PM, josep porres wrote:
> > yes, i have:
> > shared_preload_libra
On Mon, Mar 23, 2009 at 1:07 PM, josep porres 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
On Mon, Mar 23, 2009 at 1:41 PM, josep porres 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
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
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
> On Mon, Mar 23, 2009 at 1:41 PM, josep porres wrote:
> > tha
On Mon, Mar 23, 2009 at 1:56 PM, josep porres 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:
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
> On Mon, Mar 23, 2009 at 1:56 PM, josep porres wrote:
> > well, now a log with only trying to debug setting a breakpoint
>
> Hmmm - do you still have the demo s
On Tue, Mar 24, 2009 at 7:50 AM, josep porres 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.e
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 fo
by the way, after upgrading, i get the same behaviour
even executing the function in a query window created after setting the
breakpoint.
2009/3/24 josep porres
> i've just upgraded the server to 8.3.7 holding the same data directory
>
> select * from pldbg_get_proxy_info();
> "serverversionstr"
On Tue, Mar 24, 2009 at 1:42 PM, josep porres 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
asdfasdfasdfasdfasdfasdfasdfasdfasdfasd
asdfasdff
asdfasdfasdfasdfasdfasdfasdfasdfasdfasd
asdfasdff
asdfasdfasdfasdfasdfasdfasdfasdfasdfasd
asdfasdff
asdfasdfasdf
18 matches
Mail list logo
