April 10, 2016 Why do my stack traces look like this? How can I get more informative ones? | ||||
---|---|---|---|---|
| ||||
I'm getting a RangeError and the stack trace is being spectacularly unhelpful in debugging the problem, because it looks like this: core.exception.RangeError@E:\Dropbox\Projects\d\lib\wip_ansi_2.d(78): Range violation ---------------- 0x0040A240 0x00402E37 0x00402B5E 0x00402985 0x00402F29 0x0040C3A3 0x0040C367 0x0040C268 0x0040965F 0x758533AA in BaseThreadInitThunk 0x77699F72 in RtlInitializeExceptionChain 0x77699F45 in RtlInitializeExceptionChain How can I fix this, and get something human-readable? |
April 10, 2016 Re: Why do my stack traces look like this? How can I get more informative ones? | ||||
---|---|---|---|---|
| ||||
Posted in reply to pineapple | On Sunday, 10 April 2016 at 00:48:23 UTC, pineapple wrote:
> How can I fix this, and get something human-readable?
Oh, answered my own question. Appending the -g flag to dmd options makes the stack trace much prettier.
|
Copyright © 1999-2021 by the D Language Foundation