On Sunday, 5 August 2018 at 10:12:39 UTC, Alex wrote:
On Sunday, 5 August 2018 at 01:15:07 UTC, Nicholas Wilson wrote:
On Saturday, 4 August 2018 at 18:12:05 UTC, Alex wrote:
On Saturday, 4 August 2018 at 13:26:01 UTC, Nicholas Wilson
That is a very long stacks trace and combined with the very
On Sunday, 5 August 2018 at 01:15:07 UTC, Nicholas Wilson wrote:
On Saturday, 4 August 2018 at 18:12:05 UTC, Alex wrote:
On Saturday, 4 August 2018 at 13:26:01 UTC, Nicholas Wilson
That is a very long stacks trace and combined with the very
short stack trace on OSX, this is probably a stack
On Saturday, 4 August 2018 at 18:12:05 UTC, Alex wrote:
On Saturday, 4 August 2018 at 13:26:01 UTC, Nicholas Wilson
wrote:
0 ldc2 0x000106fcc4e7
llvm::sys::PrintStackTrace(llvm::raw_ostream&) + 37
1 ldc2 0x000106fcb9ea
On Saturday, 4 August 2018 at 22:50:49 UTC, kinke wrote:
On Saturday, 4 August 2018 at 18:12:05 UTC, Alex wrote:
/snap/ldc2/78/bin/ldc2(_start+0x29)[0x8b7ee9]
You haven't specified the DMD version you are using. Your LDC
is 'outdated', so make sure to first check whether it still
fails with
On Saturday, 4 August 2018 at 18:12:05 UTC, Alex wrote:
/snap/ldc2/78/bin/ldc2(_start+0x29)[0x8b7ee9]
You haven't specified the DMD version you are using. Your LDC is
'outdated', so make sure to first check whether it still fails
with an up-to-date version before potentially wasting time.
On Saturday, 4 August 2018 at 13:29:36 UTC, kinke wrote:
You're most likely hitting an ICE in the front-end (as both
compilers crash). What you can always do is invoke the compiler
in a GDB session. That's especially useful with an LDC CI build
(download:
On Saturday, 4 August 2018 at 13:26:01 UTC, Nicholas Wilson wrote:
0 ldc2 0x000106fcc4e7
llvm::sys::PrintStackTrace(llvm::raw_ostream&) + 37
1 ldc2 0x000106fcb9ea
llvm::sys::RunSignalHandlers() + 83
2 ldc2 0x000106fcc90e
On Saturday, 4 August 2018 at 13:29:36 UTC, kinke wrote:
[...] as it features debuginfos
Sorry, scrach that (it used to for the Windows CI build but
doesn't anymore).
On Saturday, 4 August 2018 at 12:21:36 UTC, Alex wrote:
I'm a little bit confused by following situation:
I have code, say around 8000 lines. Now, I'm facing a build
error which just says
dmd failed with exit code -11,
(same for ldc2, with some lines of stack information, which do
not
You're most likely hitting an ICE in the front-end (as both
compilers crash). What you can always do is invoke the compiler
in a GDB session. That's especially useful with an LDC CI build
(download:
https://github.com/ldc-developers/ldc/releases/tag/CI), as it
features debuginfos and enabled
On Saturday, 4 August 2018 at 12:21:36 UTC, Alex wrote:
Ok. Dustmite finished. But the result is again an empty file... :(
I'm a little bit confused by following situation:
I have code, say around 8000 lines. Now, I'm facing a build error
which just says
dmd failed with exit code -11,
(same for ldc2, with some lines of stack information, which do
not belong to my code)
0 ldc2
12 matches
Mail list logo
