Re: No error message in DMD 2.078.2

2018-02-13 Thread ag0aep6g via Digitalmars-d-learn

On 02/13/2018 06:51 AM, Domain wrote:

module main;

void main ()
{
     writeln("Hello");
}

Of course, this won't compile, but error message is confused:

C:\Git\hello\source>dmd app.d
app.d(5): Error:
object.Error@(0): Access Violation


This is issue 18403. You should see an error message with some 
highlighted code, but dmd crashes when it tries to print that. You can 
invoke dmd with `-color=off` to work around the issue, or go back to 
2.078.1 until we get a release with the fix.


https://issues.dlang.org/show_bug.cgi?id=18403


Re: No error message in DMD 2.078.2

2018-02-12 Thread psychoticRabbit via Digitalmars-d-learn

On Tuesday, 13 February 2018 at 05:51:05 UTC, Domain wrote:

module main;

void main ()
{
writeln("Hello");
}

Of course, this won't compile, but error message is confused:

C:\Git\hello\source>dmd app.d
app.d(5): Error:
object.Error@(0): Access Violation

0x0065445A
0x006548FE
0x0064DBD3
0x004B0B90
0x004B8A02
0x00594813
0x005797E2
0x77E40608 in RtlAllocateHeap
0x77E3EB5E in RtlAllocateHeap
0x77E2DD5A in RtlRandom
0x004E0F98
0x005B6D16
0x0047BFCA
0x005DD152


erh?

I get a good enough error message(v2.078.2)

Exit code is: 1
..Error: `writeln` is not defined, perhaps `import std.stdio;` is 
needed?


Sounds more like you have env issues.



Re: No error message in DMD 2.078.2

2018-02-12 Thread Jonathan M Davis via Digitalmars-d-learn
On Tuesday, February 13, 2018 05:51:05 Domain via Digitalmars-d-learn wrote:
> module main;
>
> void main ()
> {
>  writeln("Hello");
> }
>
> Of course, this won't compile, but error message is confused:
>
> C:\Git\hello\source>dmd app.d
> app.d(5): Error:
> object.Error@(0): Access Violation
> 
> 0x0065445A
> 0x006548FE
> 0x0064DBD3
> 0x004B0B90
> 0x004B8A02
> 0x00594813
> 0x005797E2
> 0x77E40608 in RtlAllocateHeap
> 0x77E3EB5E in RtlAllocateHeap
> 0x77E2DD5A in RtlRandom
> 0x004E0F98
> 0x005B6D16
> 0x0047BFCA
> 0x005DD152

Report it on bugzilla: https://issues.dlang.org

My guess would be that the printf that's printing the error message is being
given a null string or something along those lines, so it segfaults.

- Jonathan M Davis