digitalmars.D.debugger - ddbg: run to cursor in C::B misbehaves
- sd (10/10) Apr 25 2007 Run to cursor appears to set a permanent breakpoint instead of a tempora...
- Jascha Wetzel (6/16) Apr 25 2007 i agree. the console stays open when an exception is caught but it
- sd (4/21) Apr 26 2007 Thanks! working real good now.
- Jascha Wetzel (2/3) Apr 27 2007 yep
Run to cursor appears to set a permanent breakpoint instead of a temporary one. The gui (correctly) doesn't show it as a breakpoint, it just behaves like there's one there. Also, if you start a program with run to cursor it just runs to the first hard breakpoint or to completion if there aren't any. And finally: can the pause at the end of a console output run be emulated when run via ddbg? At the moment it just closes the console. I find that feature very useful. - S
Apr 25 2007
sd wrote:Run to cursor appears to set a permanent breakpoint instead of a temporary one. The gui (correctly) doesn't show it as a breakpoint, it just behaves like there's one there. Also, if you start a program with run to cursor it just runs to the first hard breakpoint or to completion if there aren't any.both fixed in next releaseAnd finally: can the pause at the end of a console output run be emulated when run via ddbg? At the moment it just closes the console. I find that feature very useful.i agree. the console stays open when an exception is caught but it closes when the process terminates normally. that is win32 behaviour. what Ddbg could do is to optionally break in the D runtime just before the process terminates.
Apr 25 2007
On Wed, 25 Apr 2007 19:16:40 +0100, Jascha Wetzel <"[firstname]" mainia.de> wrote:sd wrote:Thanks! working real good now.Run to cursor appears to set a permanent breakpoint instead of a temporary one. The gui (correctly) doesn't show it as a breakpoint, it just behaves like there's one there. Also, if you start a program with run to cursor it just runs to the first hard breakpoint or to completion if there aren't any.both fixed in next releaseOk, by optionally you mean a switch?And finally: can the pause at the end of a console output run be emulated when run via ddbg? At the moment it just closes the console. I find that feature very useful.i agree. the console stays open when an exception is caught but it closes when the process terminates normally. that is win32 behaviour. what Ddbg could do is to optionally break in the D runtime just before the process terminates.
Apr 26 2007
sd wrote:Ok, by optionally you mean a switch?yep
Apr 27 2007