From: | Andreas Pflug <Andreas(dot)Pflug(at)web(dot)de> |
---|---|
To: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk>, pgadmin-hackers(at)postgresql(dot)org |
Subject: | Re: pgadmin3 query tools |
Date: | 2003-04-03 18:50:39 |
Message-ID: | 3E8C827F.9060100@web.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Dave Page wrote:
>The difficulty there was mapping the pgAdmin debug levels into
>wxWindows. As 99% of the time I use Errors/SQL/Full Debug, I decided to
>include only those plus None. As for all the pgXxx created's, we
>probably don't need those as long as we do put in meaningful messages
>elsewhere. In pga2, we log every function entry on Full Debug which is
>handy if we need to figure out the call stack, but otherwise can be a
>pain.
>
It seems to me as if the debug levels could be extended. I'll have a
look at it.
>
>What do you think? I vaguely remember reading somewhere that glibc has
>some sort of call stack macro that you can use at runtime anyway... Can
>Windows do anything like that in a non-debug build?
>
>
>
Dr. Watson does it. If you got a matching debug library for a nondebug
build, you can diagnose a crashdump afterwards. Anyway, a full debug log
should do also.
Regards,
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Ian Barwick | 2003-04-03 21:19:01 | Re: help for postgreSQL in shell |
Previous Message | Dave Page | 2003-04-03 14:22:31 | Re: pgadmin2 conversion patch |