I have a program that was crashing due to a "Conversion positive
overflow", specifically calling .to!int on a too-large unsigned
value.
However it was simply crashing with an exit code (-1073740771 /
0xC41D), and I was having a heck of a time trying to debug
on Windows. (Shoutout to the
On Thursday, 31 January 2019 at 11:09:56 UTC, DanielG wrote:
I have a program that was crashing due to a "Conversion
positive overflow", specifically calling .to!int on a too-large
unsigned value.
However it was simply crashing with an exit code (-1073740771 /
0xC41D), and I was having
I can't say for sure, but there are some cases I know where you
don't get stack trace (mostly dmd bugs):
- inside module constructors `shared static this()`
- null function pointer call
On Thursday, 31 January 2019 at 11:28:40 UTC, bauss wrote:
Did you compile it with debug info? Eg. -g
Yep, I use dub for builds which does that by default. Until this
bug I was getting the usual stack traces with my project since
the beginning.
On Thursday, 31 January 2019 at 11:09:56 UTC, DanielG wrote:
However it was simply crashing with an exit code (-1073740771 /
0xC41D), and I was having a heck of a time trying to
debug on Windows. (Shoutout to the revamped WinDbg Preview,
couldn't get anything else to work!)
For Windows,
On Friday, 1 February 2019 at 09:00:32 UTC, JN wrote:
For Windows, you can try VisualD and VSCode with C++ debugger.
I tried both of those but neither seemed to work out of the gate.
I didn't take notes but my vague memory is that VisualD wasn't
picking up some local dub dependecies and/or so
