Skip site navigation (1) Skip section navigation (2)

Re: Fix debugging on EDB with latest pldebugger

From: Dave Page <dpage(at)pgadmin(dot)org>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: Fix debugging on EDB with latest pldebugger
Date: 2012-04-26 11:42:35
Message-ID: (view raw or whole thread)
Lists: pgadmin-hackers
Thanks, patch applied.

On Thu, Apr 26, 2012 at 11:51 AM, Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
> Thanks to recent changes I made to the pldebugger server-side functions, the
> EDB-specific parts of pldebugger are now linked into the same
> library as the PL/pgSQL parts. It used to produce a
> separate library, but that was inconvenient. For
> example if you had a call stack that contained both PL/pgSQL and EDB-SPL
> functions, you could not display both of them in the same debugger session.
> That's now been changed in pldebugger, but now pgAdmin refuses to debug SPL
> functions because it doesn't see in
> shared_preload_libraries line. Here's a patch that teaches pgAdmin that
> now contains all that's needed or debugging SPL code.
> I'm actually not sure it's a good idea to require shared_preload_libraries
> to contain the library; much of the debugging functionality is quite usable
> without that. If you load the library in a single session, you can set local
> breakpoints and debug in that session, for example. But this patch doesn't
> change that.
> --
>  Heikki Linnakangas
>  EnterpriseDB
> --
> Sent via pgadmin-hackers mailing list (pgadmin-hackers(at)postgresql(dot)org)
> To make changes to your subscription:

Dave Page
Twitter: @pgsnake

EnterpriseDB UK:
The Enterprise PostgreSQL Company

In response to

pgadmin-hackers by date

Next:From: Dave PageDate: 2012-04-26 11:43:13
Subject: Re: Debugger line numbering is off by one
Previous:From: Dave PageDate: 2012-04-26 11:42:22
Subject: pgAdmin III commit: Before EDBAS92,there was a separate library for SP

Privacy Policy | About PostgreSQL
Copyright © 1996-2015 The PostgreSQL Global Development Group