Thread overview
Stack traces
Sep 20, 2003
Daniel Yokomiso
Sep 20, 2003
Matthew Wilson
Sep 26, 2003
Walter
September 20, 2003
Any plans for stack traces in exceptions, specially in asserts?

Perhaps in the next release? ;)

<rant>
Right now I'm trying (again) to review deimos against the new compiler and
most of the times, when I run my tests I'm getting an error but, since
almost all my code has contracts, I know only the line of the failed
contract, not the context, it makes bug hunting very tedious.
</rant>


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.520 / Virus Database: 318 - Release Date: 18/9/2003


September 20, 2003
Make that two keen potential strack tracers ...

"Daniel Yokomiso" <daniel_yokomiso@yahoo.com.br> wrote in message news:bkgbk0$1pk7$1@digitaldaemon.com...
> Any plans for stack traces in exceptions, specially in asserts?
>
> Perhaps in the next release? ;)
>
> <rant>
> Right now I'm trying (again) to review deimos against the new compiler and
> most of the times, when I run my tests I'm getting an error but, since
> almost all my code has contracts, I know only the line of the failed
> contract, not the context, it makes bug hunting very tedious.
> </rant>
>
>
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.520 / Virus Database: 318 - Release Date: 18/9/2003
>
>


September 26, 2003
"Daniel Yokomiso" <daniel_yokomiso@yahoo.com.br> wrote in message news:bkgbk0$1pk7$1@digitaldaemon.com...
> Any plans for stack traces in exceptions, specially in asserts?
>
> Perhaps in the next release? ;)

The next release is going to be a bug fix.

> <rant>
> Right now I'm trying (again) to review deimos against the new compiler and
> most of the times, when I run my tests I'm getting an error but, since
> almost all my code has contracts, I know only the line of the failed
> contract, not the context, it makes bug hunting very tedious.
> </rant>

What to do is take phobos\dmain2.d, and remove the catch for the exceptions. Recompile. Compile your program with -g. Run under Windbg.exe, and then when it faults, load the 'calls' window, and you should see a stack trace.