call traceback is indecipherable garbage

[Steven Schveighoffer]

On 1/25/22 9:20 PM, forkit wrote:
> has anyone ever considered getting rid of the indecipherable garbage 
> after ----
> (or having some compile time option to not output it?)
> 
> I don't want to see it.
> 
> I sure don't want my end-users to see it either.
> 
> 
> / --
> 
> module test;
> import std;
> void main()
> {
>      File f = File("nosuchfile");
> }
> 
> // --
> 
> Exit code is: 1
> 
> std.exception.ErrnoException at std\stdio.d(545): Cannot open file 
> `nosuchfile' in mode `rb' (No such file or directory)
> ----------------
> 0x000000013FB5F836
> 0x000000013FB53423
> 0x000000013FB51269
> 0x000000013FB51057
> 0x000000013FB5ECB3
> 0x000000013FB5EB2F
> 0x000000013FB5EC1B
> 0x000000013FB5EB2F
> 0x000000013FB5EA56
> 0x000000013FB53171
> 0x000000013FB51094
> 0x000000013FBD2F68
> 0x0000000076F9556D in BaseThreadInitThunk
> 0x00000000771F372D in RtlUserThreadStart
> 

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