ddbg: run to cursor in C::B misbehaves

sd nobody at here.com
Thu Apr 26 07:12:31 PDT 2007


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
Thanks! working real good now.

>
>> 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.
Ok, by optionally you mean a switch?


More information about the Digitalmars-d-debugger mailing list