Is there a way to get stack traces on exceptions in D2?

Nick Sabalausky wrote:

> Is there a way to get stack traces on exceptions in D2?
What OS.

I'm on linux and I get stack traces.

"Rory Mcguire" <rjmcguire@gm_no_ail.com> wrote in message news:i2rafu$20lv$1@digitalmars.com...
> Nick Sabalausky wrote:
>
>> Is there a way to get stack traces on exceptions in D2?
> What OS.
>
> I'm on linux and I get stack traces.

Windows.

Must be a debug-only thing though (not sure why I thought otherwise). I've been unable to actually build in debug mode though, because 2.046 gives me phobos errors if I use debug mode, and 2.076 can't do array(filter()) which is a breaker for me. I guess I could try 2.045.

"Nick Sabalausky" <a@a.a> wrote in message news:i2rbht$22v4$1@digitalmars.com...
> "Rory Mcguire" <rjmcguire@gm_no_ail.com> wrote in message news:i2rafu$20lv$1@digitalmars.com...
>> Nick Sabalausky wrote:
>>
>>> Is there a way to get stack traces on exceptions in D2?
>> What OS.
>>
>> I'm on linux and I get stack traces.
>
> Windows.
>
> Must be a debug-only thing though (not sure why I thought otherwise). I've been unable to actually build in debug mode though, because 2.046 gives me phobos errors if I use debug mode, and 2.076 can't do array(filter()) which is a breaker for me. I guess I could try 2.045.

Hmm, weird, I'm not getting the Phobos error with debug-mode on 2.076 now. But still not getting stack traces though, even with both -debug and -g

Nick Sabalausky wrote:

> "Nick Sabalausky" <a@a.a> wrote in message news:i2rbht$22v4$1@digitalmars.com...
>> "Rory Mcguire" <rjmcguire@gm_no_ail.com> wrote in message news:i2rafu$20lv$1@digitalmars.com...
>>> Nick Sabalausky wrote:
>>>
>>>> Is there a way to get stack traces on exceptions in D2?
>>> What OS.
>>>
>>> I'm on linux and I get stack traces.
>>
>> Windows.
>>
>> Must be a debug-only thing though (not sure why I thought otherwise).
>> I've been unable to actually build in debug mode though, because 2.046
>> gives me phobos errors if I use debug mode, and 2.076 can't do
>> array(filter()) which is a breaker for me. I guess I could try 2.045.
> 
> Hmm, weird, I'm not getting the Phobos error with debug-mode on 2.076 now. But still not getting stack traces though, even with both -debug and -g

interesting, I get them on 2.046 with and without -debug but not with - release.

Nick Sabalausky wrote:
> Is there a way to get stack traces on exceptions in D2?
> 
> 
It's not yet implemented on Windows. Mainly because Sean hasn't had enough free time.

On 2010-07-29 13:44, Don wrote:
> Nick Sabalausky wrote:
>> Is there a way to get stack traces on exceptions in D2?
>>
>>
> It's not yet implemented on Windows. Mainly because Sean hasn't had
> enough free time.

Does tango have stack traces on windows? Or I guess it doesn't matter, can't use the code from tango anyway because of license issues. That's the problem with druntime, it's a fork of the tango runtime that evolves on its own path, making the runtimes incompatible again.

-- 
/Jacob Carlborg

"Jacob Carlborg" <doob@me.com> wrote in message news:i2sfk4$185q$1@digitalmars.com...
> On 2010-07-29 13:44, Don wrote:
>> Nick Sabalausky wrote:
>>> Is there a way to get stack traces on exceptions in D2?
>>>
>>>
>> It's not yet implemented on Windows. Mainly because Sean hasn't had enough free time.
>
> Does tango have stack traces on windows?

Yes.

> Or I guess it doesn't matter, can't use the code from tango anyway because of license issues. That's the problem with druntime, it's a fork of the tango runtime that evolves on its own path, making the runtimes incompatible again.
>