call traceback is indecipherable garbage
schveiguy at gmail.com
Wed Jan 26 03:45:01 UTC 2022
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)
> 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?
More information about the Digitalmars-d