OSX users out there? Serious bug (I think)

[Paolo Invernizzi]

On Sunday, 31 March 2013 at 20:02:40 UTC, monarch_dodra wrote:
> This is a two part post.
>
> First, I wanted to pol how many users out there were developing 
> under OSX? The threads seem to indicated users under windows or 
> Linux, but I've never heard of anybody under OSX. So who has or 
> is developing under OSX? Anybody?
>
> I also wanted to know if you had any "stability" problems. It 
> seems there are strange bugs with the OSX realease every now 
> and then, and those are only the ones we "see". Has anybody 
> tried D with a "relatively" large project? No problems?
>
> The second part of this post is about a specific (OSX related) 
> bug. I don't like drawing attention to it such as this, as I 
> know we are all busy, but I think this one is serious enough to 
> try to push for its investigation: 
> http://d.puremagic.com/issues/show_bug.cgi?id=9720
>
> The reason I'm worried about this bug is that the only 
> condition that seems to trigger it passing an object that has a 
> destructor. I find this is very bothersome, because it can 
> happen with perfectly safe code, and its "observable condition" 
> is perfectly undefined. Finally, it only appears in -O, biting 
> you in the ass in the worst possible moment.
>
> Seeing that this bug exists, I'd have 0 faith to use D under 
> OSX. May I kindly request that those with the required 
> knowledge to fix this bug try to investigate it? Sorry for 
> insisting/asking...

We use D at work, since pre-1, and right now we are using it in 
Windows, Linux mainly and OSX: we have a discrete codebase, and 
we are using it for production code in real products.

Actually on OSX I'm using LDC, because simply I can't use objc 
bindings with DMD (random stack corruptions), and I'm a little 
too under time pressure to investigate the issue.

I can confirm that we have some problems with -O code: actually 
we are avoiding it, and we are simply stuck with no optimisations 
at all...

/Paolo