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

SVN Commit by dpage: r7838 - trunk/pgadmin3/pgadmin/debugger

From: svn(at)pgadmin(dot)org
To: pgadmin-hackers(at)postgresql(dot)org
Subject: SVN Commit by dpage: r7838 - trunk/pgadmin3/pgadmin/debugger
Date: 2009-05-05 10:05:57
Message-ID: 200905051005.n45A5vUd027706@developer.pgadmin.org (view raw or flat)
Thread:
Lists: pgadmin-hackers
Author: dpage

Date: 2009-05-05 11:05:57 +0100 (Tue, 05 May 2009)

New Revision: 7838

Revision summary: http://svn.pgadmin.org/cgi-bin/viewcvs.cgi/?rev=7838&view=rev

Log:
Please find the patch for an issue related to the debugger in gtk (linux).

Please find the steps to reproduce this issue:
1. Right click any pl/pgsql function without any parameter. Select
   Debugging->Debug.
2. It will open the debugger window.
3. Select File->Exit from menu.
4. Press 'yes' for the below question:
   "Are you sure you wish to abort the debugging session?
    This will abort the function currently being debugged."
5. Close main window.
6. This will gives you the following message and wait for all threads to be
   getting killed.
   "TIME WITH TIMEZONE: Debug: 1 threads were not terminated by the application."

I found that - we're creating two dbgPgConn object, one in ctlCodeWindow and the
other in dlgDirectDbg. Both creates their own threads (dbgThread object).

When we abort debugging, somehow it is not calling the Close function of the
dlgDirectDbg only on linux (wxGTK). Hence, the thread created in dlgDirectDbg is
not get killed/stopped in this case.

[Ashesh Vashi]



Modified:
   trunk/pgadmin3/pgadmin/debugger/ctlCodeWindow.cpp

pgadmin-hackers by date

Next:From: svnDate: 2009-05-05 10:06:31
Subject: SVN Commit by dpage: r7839 - trunk/pgadmin3/pgadmin/debugger
Previous:From: Dave PageDate: 2009-05-05 09:43:37
Subject: Re: Sorry...

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