Jump to page: 1 2
Thread overview
_Unwind_RaiseException
Sep 01
Oleg B
Sep 01
Oleg B
Sep 01
Oleg B
Sep 01
Joakim
Sep 01
Oleg B
Sep 01
Oleg B
Sep 01
Joakim
Sep 01
Oleg B
Sep 01
kinke
Sep 02
Joakim
Sep 05
Oleg B
Sep 05
Joakim
Sep 05
Oleg B
September 01
Hello. I work on project, that works on ARMv7 (Raspberry PI 2). Some times I get error in random places (build to build in different place, no rebuild - stable error place):

Fatal error in EH code: _Unwind_RaiseException failed with reason code: 9 Aborted

I found few issues on github

https://github.com/ldc-developers/ldc/issues/2208
https://github.com/ldc-developers/ldc/issues/2058
https://github.com/ldc-developers/ldc/issues/2024

But I don't understand how workaround this.
My ldc2.conf have no special flags, I don't use optimization.

default:
{
    switches = [
        "-I/usr/include/d/ldc",
        "-I/usr/include/d",
        "-mtriple=arm-linux-gnueabihf",
        "-gcc=arm-linux-gnueabihf-gcc",
        "-L-L/home/deviator/workspace/arm-linux-gnueabihf",
        "-defaultlib=phobos2-ldc,druntime-ldc",
        "-debuglib=phobos2-ldc-debug,druntime-ldc-debug"
    ];
};

Trying add "-mattr=+strict-align" has no effect.
I see only one way for fix it: don't use exceptions. But it require a lot of work on rewriting existing code. May be this problem has more elegant solution?
September 01
On Friday, 1 September 2017 at 10:04:51 UTC, Oleg B wrote:
> Hello. I work on project, that works on ARMv7 (Raspberry PI 2). Some times I get error in random places (build to build in different place, no rebuild - stable error place):
>
> [...]

What's the output of `ldc2 --version` ?
September 01
On Friday, 1 September 2017 at 10:14:54 UTC, Petar Kirov [ZombineDev] wrote:
> What's the output of `ldc2 --version` ?

LDC - the LLVM D compiler (1.3.0):
  based on DMD v2.073.2 and LLVM 4.0.0
  built with LDC - the LLVM D compiler (1.3.0)
  Default target: x86_64-unknown-linux-gnu
  Host CPU: skylake

last ldc from fedora repo
September 01
On Friday, 1 September 2017 at 10:19:07 UTC, Oleg B wrote:
> On Friday, 1 September 2017 at 10:14:54 UTC, Petar Kirov [ZombineDev] wrote:
>> What's the output of `ldc2 --version` ?
>
> LDC - the LLVM D compiler (1.3.0):
>   based on DMD v2.073.2 and LLVM 4.0.0
>   built with LDC - the LLVM D compiler (1.3.0)
>   Default target: x86_64-unknown-linux-gnu
>   Host CPU: skylake
>
> last ldc from fedora repo

Can you try https://github.com/ldc-developers/ldc/releases/tag/v1.4.0-beta1 ?

Cross-compilation should be easier if you use the newly added ldc-build-runtime tool. There's a wiki page describing how it can be used: https://wiki.dlang.org/Building_LDC_runtime_libraries
September 01
On Friday, 1 September 2017 at 10:04:51 UTC, Oleg B wrote:
> Hello. I work on project, that works on ARMv7 (Raspberry PI 2). Some times I get error in random places (build to build in different place, no rebuild - stable error place):
>
> [...]

It sounds like you have some memory corruption somewhere, doubt the issue is in exceptions. Can you try running the stdlib tests and see if those all pass?  Easiest would be 1.4 beta with instructions Petar linked you to.
September 01
On Friday, 1 September 2017 at 10:44:59 UTC, Petar Kirov [ZombineDev] wrote:
> Can you try https://github.com/ldc-developers/ldc/releases/tag/v1.4.0-beta1 ?
>
> Cross-compilation should be easier if you use the newly added ldc-build-runtime tool. There's a wiki page describing how it can be used: https://wiki.dlang.org/Building_LDC_runtime_libraries

Yes, I try it now, but this error is difficult to catch and, I think, if issues don't closed and in change log no information about this error it can occur again.
September 01
On Friday, 1 September 2017 at 15:36:55 UTC, Joakim wrote:
> Can you try running the stdlib tests and see if those all pass?
> Easiest would be 1.4 beta with instructions Petar linked you to.

How I can do this with minimal work?) I need to compile libs with -unittest flag and run empty file (void main(){}) on RPI?
September 01
On Friday, 1 September 2017 at 15:36:55 UTC, Joakim wrote:
> Can you try running the stdlib tests and see if those all pass?

I build phobos and druntime with -unittest flag and run on RPI `void main(){}`
and have this

./test
Not safe to migrate Fibers between Threads on your system. Consider setting version CheckFiberMigration for this system in thread.d

No more messages. I think all tests passed?
September 01
On Friday, 1 September 2017 at 18:14:58 UTC, Oleg B wrote:
> On Friday, 1 September 2017 at 15:36:55 UTC, Joakim wrote:
>> Can you try running the stdlib tests and see if those all pass?
>
> I build phobos and druntime with -unittest flag and run on RPI `void main(){}`
> and have this
>
> ./test
> Not safe to migrate Fibers between Threads on your system. Consider setting version CheckFiberMigration for this system in thread.d
>
> No more messages. I think all tests passed?

Looks like at least core.thread ran, better to use the test runner to make sure.  Just follow the instructions from that wiki page, there's even an example for Android.  Simply replace with your toolchain and flags.  You don't even need to build ldc, can use the ldc 1.4 beta release.
September 01
On Friday, 1 September 2017 at 19:28:51 UTC, Joakim wrote:
> You don't even need to build ldc, can use the ldc 1.4 beta release.

I know, I build phobos and druntime on host x86. Run test on RPI.

« First   ‹ Prev
1 2