On Wednesday, 26 January 2022 at 03:33:31 UTC, H. S. Teoh wrote:
>
> Running with `dmd -g -run test.d` produces:
>
> ....
>
> T

Interesting. Thanks for mentioning that -g option.

Still, it makes complete sense to me, that a stack trace dump is 'debugging material', and that -release should print only the exeption, and nothing else.

Surely I'm not the only one who has come to that conclusion :-(

On Wednesday, 26 January 2022 at 03:45:01 UTC, Steven Schveighoffer wrote:
>
> Regardless of the "correct" way to deal with this, I agree with you that printing code addresses is not helpful. I'm assuming this is Windows? Is there nothing better that can be done?
>
> -Steve

You mean stop using Windows?

On Wed, Jan 26, 2022 at 03:51:55AM +0000, forkit via Digitalmars-d wrote: [...]
> Still, it makes complete sense to me, that a stack trace dump is 'debugging material', and that -release should print only the exeption, and nothing else.

It's easy, just wrap your main() in a try-catch block:

	int main() {
		try {
			// ... rest of code goes here
			return 0;
		} catch(Exception e) {
			writeln("Error: %s", e.msg);
			return 1;
		}
	}


T

-- 
Your inconsistency is the only consistent thing about you! -- KD

On Wednesday, 26 January 2022 at 04:25:47 UTC, H. S. Teoh wrote:
>
> It's easy, just wrap your main() in a try-catch block:
>
> 	int main() {
> 		try {
> 			// ... rest of code goes here
> 			return 0;
> 		} catch(Exception e) {
> 			writeln("Error: %s", e.msg);
> 			return 1;
> 		}
> 	}
>
>
> T

great!

.. now my 2 little lines of code, has turned into all this peripheral nonesense, just to avoid displaying the useless stack dump.

;-(

// --
module test;
import std;

int main()
{
    try
    {
        auto f = File("d://tewxt.txt").byLine;
        f.take(1).each!writeln;

        return 0;
    }
    catch(Exception e)
    {
        writeln("Error: %s", e.msg);
        return 1;
    }
}
// ---

On Wednesday, 26 January 2022 at 05:17:48 UTC, forkit wrote:

>
> .. now my 2 little lines of code, has turned into all this peripheral nonesense, just to avoid displaying the useless stack dump.

There is currently an open bug which prevents a stack trace - just link a DLL statically with an initialized runtime in it :D
https://issues.dlang.org/show_bug.cgi?id=22181

On Wednesday, 26 January 2022 at 02:20:17 UTC, forkit wrote:
>
btw. I really like how Rust does it:

just set an environment variable (set RUST_BACKTRACE=1)

then run your program, and it will dump the backtrace, when you run your program.