Hi,

I have a shared object (of DInotify) compiled with ldc2.

I have a program (me-tv) which seems to work when compiled with ldc2.

If I compile the program (me-tv) with dmd then it throws a SIGSEGV seemingly
in

_D3std4file15DirIteratorImpl5frontMFNdNfZSQBoQBn8DirEntry

in DInotify. Is this what I should expect?


-- 
Russel.
==========================================
Dr Russel Winder      t: +44 20 7585 2200
41 Buckmaster Road    m: +44 7770 465 077
London SW11 1EN, UK   w: www.russel.org.uk

On Tuesday, 22 May 2018 at 16:17:48 UTC, Russel Winder wrote:
> Hi,
>
> I have a shared object (of DInotify) compiled with ldc2.
>
> I have a program (me-tv) which seems to work when compiled with ldc2.
>
> If I compile the program (me-tv) with dmd then it throws a SIGSEGV seemingly
> in
>
> _D3std4file15DirIteratorImpl5frontMFNdNfZSQBoQBn8DirEntry
>
> in DInotify.

It looks like a regression we encountered @dlang-community too. The bugzilla for this is: https://issues.dlang.org/show_bug.cgi?id=18667.

> Is this what I should expect?

I'm tempted to say "yes" since the bug is not fixed.

On Tuesday, 22 May 2018 at 16:17:48 UTC, Russel Winder wrote:
> Hi,
>
> I have a shared object (of DInotify) compiled with ldc2.
>
> I have a program (me-tv) which seems to work when compiled with ldc2.
>
> If I compile the program (me-tv) with dmd then it throws a SIGSEGV seemingly
> in
>
> _D3std4file15DirIteratorImpl5frontMFNdNfZSQBoQBn8DirEntry
>
> in DInotify. Is this what I should expect?

LDC and DMD are ABI incompatible. Also, different compiler versions of the same vendor are ABI incompatible (sometimes they are compatible).
Things may or may not work when different pieces of the program are compiled with a different compiler (which is what you are doing here).

- Johan