Re: [pgAdmin4][Patch]: To fix the issue in Debugger module

From: Dave Page <dpage(at)pgadmin(dot)org>
To: Murtuza Zabuawala <murtuza(dot)zabuawala(at)enterprisedb(dot)com>
Cc: pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: [pgAdmin4][Patch]: To fix the issue in Debugger module
Date: 2017-12-02 05:12:36
Message-ID: CA+OCxozo8+UzNfmDpTE+ZoRfmw_5=ELPeF31DOWQP2QR7brqYQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

Hi

On Thursday, November 30, 2017, Murtuza Zabuawala <
murtuza(dot)zabuawala(at)enterprisedb(dot)com> wrote:

> Hi,
>
> PFA patch to fix the issue where debugger failed to run when user tries to
> debug the function which call itself recursively.
> RM#2524
>

This seems to fix the recursion problem, but walking the stack doesn't work
- no matter which frame I click on, the highlighted source code line
remains that of the top frame, as does the value of in_val on the
Parameters tab.

Thanks.

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Attachment Content-Type Size
Screen Shot 2017-12-01 at 15.32.05.png image/png 144.8 KB

In response to

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Dave Page 2017-12-02 05:12:37 Re: [pgAdmin4][Patch]: Remove default 'Altertify JS' header from debugger related error alerts
Previous Message Dave Page 2017-12-02 05:12:29 Re: [pgAdmin4][Patch]: RM #2849 - Allow editing of data on tables with OIDs but no primary key