Re: Distribute debug information so I can get informative stack traces?
On Monday, 27 August 2018 at 22:46:31 UTC, tide wrote: On Monday, 27 August 2018 at 22:37:53 UTC, spikespaz wrote: I am compiling my project's executables with `-g`, so it outputs `pdb` files. I read that this is necessary to get a useful stack trace. When a user reports an issue, my program gives them a link where the issue body is pre-filled with the crash exception information. Example: https://github.com/spikespaz/search-deflector/issues/10 For some reason though, their reports don't have all of the call stack information that I see when I crash during development. How can I make my program give verbose stack traces like Python, so I can determine what the issue is when users report problems? Phobos isn't built with debug info. You'd have to build it yourself with the debug info and link to that instead. I am using LDC2, maybe that makes a difference, but I do get Phobos debug info on my machine. I should have clarified that it just doesn't appear to work on any other machine besides mine. Is there a better way to do this?
Re: Distribute debug information so I can get informative stack traces?
On Monday, 27 August 2018 at 22:37:53 UTC, spikespaz wrote: I am compiling my project's executables with `-g`, so it outputs `pdb` files. I read that this is necessary to get a useful stack trace. When a user reports an issue, my program gives them a link where the issue body is pre-filled with the crash exception information. Example: https://github.com/spikespaz/search-deflector/issues/10 For some reason though, their reports don't have all of the call stack information that I see when I crash during development. How can I make my program give verbose stack traces like Python, so I can determine what the issue is when users report problems? Phobos isn't built with debug info. You'd have to build it yourself with the debug info and link to that instead.
Distribute debug information so I can get informative stack traces?
I am compiling my project's executables with `-g`, so it outputs `pdb` files. I read that this is necessary to get a useful stack trace. When a user reports an issue, my program gives them a link where the issue body is pre-filled with the crash exception information. Example: https://github.com/spikespaz/search-deflector/issues/10 For some reason though, their reports don't have all of the call stack information that I see when I crash during development. How can I make my program give verbose stack traces like Python, so I can determine what the issue is when users report problems?
