Обсуждение: pldebugger blank code issue
Hello dear list,
I'm having trouble after setting up pldebugger git-current (eb754b6ba9a1c18e7bc4ddf521408be06768c697) commit in a Ubuntu 10.04.01 x86_64 box. Server versión is 9.1.5.
The issue is that once I start debugging a PLPgSQL function within pgAdmin, once it goes one level down the call stack, the given function's code isn't shown despite being a proper plpgsql function. You can run it step by step or continue, and execution is correct (even DBMS messages are displayed in the bottom pane), but I just can't see the code displayed in the main pane. If I manually click the original (main) function in the right pane, his code is shown properly. It seems that certain functions are forbidden from being shown in the main pane.
I tested this setup with pgAdmin 1.14.0, 1.14.3 and 1.16.0-beta4.
Any idea anyone?
On the side, I see a lot of people having problems these days with 9.1.x releases. Is current code production-ready?
Thanks in advance,
--
I'm having trouble after setting up pldebugger git-current (eb754b6ba9a1c18e7bc4ddf521408be06768c697) commit in a Ubuntu 10.04.01 x86_64 box. Server versión is 9.1.5.
The issue is that once I start debugging a PLPgSQL function within pgAdmin, once it goes one level down the call stack, the given function's code isn't shown despite being a proper plpgsql function. You can run it step by step or continue, and execution is correct (even DBMS messages are displayed in the bottom pane), but I just can't see the code displayed in the main pane. If I manually click the original (main) function in the right pane, his code is shown properly. It seems that certain functions are forbidden from being shown in the main pane.
I tested this setup with pgAdmin 1.14.0, 1.14.3 and 1.16.0-beta4.
Any idea anyone?
On the side, I see a lot of people having problems these days with 9.1.x releases. Is current code production-ready?
Thanks in advance,
--
Jon Garate
On Wed, Sep 5, 2012 at 12:31 PM, Jon Garate <jon@proyelia.com> wrote: > Hello dear list, > > I'm having trouble after setting up pldebugger git-current > (eb754b6ba9a1c18e7bc4ddf521408be06768c697) commit in a Ubuntu 10.04.01 > x86_64 box. Server versión is 9.1.5. > The issue is that once I start debugging a PLPgSQL function within pgAdmin, > once it goes one level down the call stack, the given function's code isn't > shown despite being a proper plpgsql function. You can run it step by step > or continue, and execution is correct (even DBMS messages are displayed in > the bottom pane), but I just can't see the code displayed in the main pane. > If I manually click the original (main) function in the right pane, his code > is shown properly. It seems that certain functions are forbidden from being > shown in the main pane. > I tested this setup with pgAdmin 1.14.0, 1.14.3 and 1.16.0-beta4. > Any idea anyone? Use the PRE_9_2 branch with 9.1, not master. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
I did so before testing master (which build a single .so file). In the case of the PRE_9_2 branch, I got 3 .so's
When I updated the configuration to load those .so's I got a undefined symbol error when restarting PostgreSQL. Could it be that I only need to load a single .so in that case as well?
--
When I updated the configuration to load those .so's I got a undefined symbol error when restarting PostgreSQL. Could it be that I only need to load a single .so in that case as well?
2012/9/5 Dave Page <dpage@pgadmin.org>
On Wed, Sep 5, 2012 at 12:31 PM, Jon Garate <jon@proyelia.com> wrote:Use the PRE_9_2 branch with 9.1, not master.
> Hello dear list,
>
> I'm having trouble after setting up pldebugger git-current
> (eb754b6ba9a1c18e7bc4ddf521408be06768c697) commit in a Ubuntu 10.04.01
> x86_64 box. Server versión is 9.1.5.
> The issue is that once I start debugging a PLPgSQL function within pgAdmin,
> once it goes one level down the call stack, the given function's code isn't
> shown despite being a proper plpgsql function. You can run it step by step
> or continue, and execution is correct (even DBMS messages are displayed in
> the bottom pane), but I just can't see the code displayed in the main pane.
> If I manually click the original (main) function in the right pane, his code
> is shown properly. It seems that certain functions are forbidden from being
> shown in the main pane.
> I tested this setup with pgAdmin 1.14.0, 1.14.3 and 1.16.0-beta4.
> Any idea anyone?
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Jon Garate
PROYELIA. Parque tecnológico Miramón. P. Mikeletegi 56. 20009 Donostia-San Sebastián [mapa]
On Wed, Sep 5, 2012 at 12:45 PM, Jon Garate <jon@proyelia.com> wrote: > I did so before testing master (which build a single .so file). In the case > of the PRE_9_2 branch, I got 3 .so's > When I updated the configuration to load those .so's I got a undefined > symbol error when restarting PostgreSQL. Could it be that I only need to > load a single .so in that case as well? Yes. Please see README.pldebugger in the source tree. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Just tracked down the issue. The debugger won't display code if it contains characters with accent (in the case of spanish charset at least). ¿I guess this extends to the whole non-ascii charset? Other than that, looks good.
Thanks pgadmin-hackers!
--
Thanks pgadmin-hackers!
2012/9/5 Dave Page <dpage@pgadmin.org>
On Wed, Sep 5, 2012 at 12:45 PM, Jon Garate <jon@proyelia.com> wrote:Yes. Please see README.pldebugger in the source tree.
> I did so before testing master (which build a single .so file). In the case
> of the PRE_9_2 branch, I got 3 .so's
> When I updated the configuration to load those .so's I got a undefined
> symbol error when restarting PostgreSQL. Could it be that I only need to
> load a single .so in that case as well?
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Jon Garate
PROYELIA. Parque tecnológico Miramón. P. Mikeletegi 56. 20009 Donostia-San Sebastián [mapa]
Tested and confirmed, code displays correctly in the case of pgAdmin 1.14.3 in a UTF-8 encoded DB.
--
2012/9/11 Jon Garate <jon@proyelia.com>
Just tracked down the issue. The debugger won't display code if it contains characters with accent (in the case of spanish charset at least). ¿I guess this extends to the whole non-ascii charset? Other than that, looks good.
Thanks pgadmin-hackers!2012/9/5 Dave Page <dpage@pgadmin.org>On Wed, Sep 5, 2012 at 12:45 PM, Jon Garate <jon@proyelia.com> wrote:Yes. Please see README.pldebugger in the source tree.
> I did so before testing master (which build a single .so file). In the case
> of the PRE_9_2 branch, I got 3 .so's
> When I updated the configuration to load those .so's I got a undefined
> symbol error when restarting PostgreSQL. Could it be that I only need to
> load a single .so in that case as well?
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company--Jon Garate
PROYELIA. Parque tecnológico Miramón. P. Mikeletegi 56. 20009 Donostia-San Sebastián [mapa]
--
Jon Garate
PROYELIA. Parque tecnológico Miramón. P. Mikeletegi 56. 20009 Donostia-San Sebastián [mapa]