• sd <nobody here.com> Apr 25 2007
• Jascha Wetzel <"[firstname]" mainia.de> Apr 25 2007
• sd <nobody here.com> Apr 26 2007
• Jascha Wetzel <"[firstname]" mainia.de> Apr 27 2007

sd <nobody here.com> writes:

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

Jascha Wetzel <"[firstname]" mainia.de> writes:

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 release

 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.

sd <nobody here.com> writes:

On Wed, 25 Apr 2007 19:16:40 +0100, Jascha Wetzel  
<"[firstname]" mainia.de> wrote:

 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 release



 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.

Jascha Wetzel <"[firstname]" mainia.de> writes:

sd wrote:
 Ok, by optionally you mean a switch?


yep