On Thursday, 14 June 2018 at 11:30:46 UTC, DigitalDesigns wrote:
object.Error@(0): Access Violation
0x00415999
0x0040A3B7
0x00518A2D
0x005751FD
0x005ABA41
0x005ABAEB
0x00525136
0x005246D6
0x005253E2
0x0066509D
0x00664F38
0x00529F68
0x77018744 in BaseThreadInitThunk
0x77C5582D in
On 14.06.2018 13:30, DigitalDesigns wrote:
All I know is that using the code
static foreach(a; ["wchar", "ushort"])
mixin("void bar("~a~" value) { foo(); }");
is what is causing it. Manually giving the functions works fine.
This works:
void foo(){}
static foreach(a; ["wchar", "ushort"]
On Thursday, 14 June 2018 at 11:30:46 UTC, DigitalDesigns wrote:
object.Error@(0): Access Violation
0x00415999
0x0040A3B7
0x00518A2D
0x005751FD
0x005ABA41
0x005ABAEB
0x00525136
0x005246D6
0x005253E2
0x0066509D
0x00664F38
0x00529F68
0x77018744 in BaseThreadInitThunk
0x77C5582D in
On Thursday, 14 June 2018 at 12:12:34 UTC, Timon Gehr wrote:
On 14.06.2018 13:30, DigitalDesigns wrote:
All I know is that using the code
static foreach(a; ["wchar", "ushort"])
mixin("void bar("~a~" value) { foo(); }");
is what is causing it. Manually giving the functions works
fine.
I am getting the compiler to crash from a different problem
after I moved some files around. I have no idea where the error
is now.
There was a module that was included that was crashing the
compiler for some reason. When I removed it, which wasn't part of
the original project the compiler
On Friday, June 15, 2018 02:31:49 DigitalDesigns via Digitalmars-d wrote:
> > I am getting the compiler to crash from a different problem
> > after I moved some files around. I have no idea where the error
> > is now.
>
> There was a module that was included that was crashing the
> compiler for som
On Friday, June 15, 2018 02:19:51 DigitalDesigns via Digitalmars-d wrote:
> Why can't the compiler give a stack trace? Any information is
> better than none!
It's not giving a stack trace with symbol names, because it wasn't compiled
with debug symbols enabled.
- Jonathan M Davis
On Friday, 15 June 2018 at 02:47:56 UTC, Jonathan M Davis wrote:
On Friday, June 15, 2018 02:31:49 DigitalDesigns via
Digitalmars-d wrote:
> I am getting the compiler to crash from a different problem
> after I moved some files around. I have no idea where the
> error is now.
There was a modu
On Friday, June 15, 2018 03:54:34 DigitalDesigns via Digitalmars-d wrote:
> On Friday, 15 June 2018 at 02:47:56 UTC, Jonathan M Davis wrote:
> > On Friday, June 15, 2018 02:31:49 DigitalDesigns via
> >
> > Digitalmars-d wrote:
> >> > I am getting the compiler to crash from a different problem
> >>
On Friday, 15 June 2018 at 03:54:34 UTC, DigitalDesigns wrote:
So, it should be very important to have some type of info that
connects the error to what the compiler was doing. With large
problems it is not easy to reduce to a test case that shows the
problem directly.
In my experience as a l
On Friday, 15 June 2018 at 04:19:28 UTC, Vladimir Panteleev wrote:
On Friday, 15 June 2018 at 03:54:34 UTC, DigitalDesigns wrote:
So, it should be very important to have some type of info that
connects the error to what the compiler was doing. With large
problems it is not easy to reduce to a t
11 matches
Mail list logo
