Jump to page: 1 2
Thread overview
[Bug 273] Unexplained crash in generated binary
September 29
https://bugzilla.gdcproject.org/show_bug.cgi?id=273

Iain Buclaw <ibuclaw@gdcproject.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED

--- Comment #1 from Iain Buclaw <ibuclaw@gdcproject.org> ---
Ouch, looks like some horrid stack stomping is going on.

---
(gdb) p box.children
$1 = {0x7ffff7ecb020, 0x7ffff7ecb040}
(gdb) n
(gdb) p box.children
$2 = {0x7ffff7ecb080, 0x5555557c71a0}
---

-- 
You are receiving this mail because:
You are watching all bug changes.
September 29
https://bugzilla.gdcproject.org/show_bug.cgi?id=273

--- Comment #2 from Iain Buclaw <ibuclaw@gdcproject.org> ---
Oh wait, no.  This is a bug in the GC.

-- 
You are receiving this mail because:
You are watching all bug changes.
September 30
https://bugzilla.gdcproject.org/show_bug.cgi?id=273

--- Comment #3 from Sebastien Alaiwan <sebastien.alaiwan@gmail.com> ---
Hi Iain, thanks for looking. Were you able to reproduce it with the git master HEAD?

-- 
You are receiving this mail because:
You are watching all bug changes.
September 30
https://bugzilla.gdcproject.org/show_bug.cgi?id=273

--- Comment #4 from Iain Buclaw <ibuclaw@gdcproject.org> ---
I can't reproduce on master locally, though I'd like to check the gdc-7 branch specifically. As this is a compiler packaged for Ubuntu, cannot rule out that some distribution-specific patches have an effect on the result.

If there's a specific configuration that defeats the GC's ability to determine live objects from unreferenced, I'd like to know about it.

This reminds me of
https://github.com/D-Programming-GDC/GDC/commit/5021b8d031fcacac52ee43d83508a5d2856606cd
- that patch is not related, but it could be a similar symptom (scanning for
pointers at unaligned offsets).

-- 
You are receiving this mail because:
You are watching all bug changes.
October 01
On Saturday, 30 September 2017 at 08:08:29 UTC, Iain Buclaw wrote:
> --- Comment #4 from Iain Buclaw <ibuclaw@gdcproject.org> ---
> If there's a specific configuration that defeats the GC's ability to determine live objects from unreferenced, I'd like to know about it.

This one is blocking us (luckily, only on one project).
Any idea for a workaround?

We can't downgrade to gdc-6 because https://bugzilla.gdcproject.org/show_bug.cgi?id=250 (fixed on master, not backported to gdc-6).

Thanks!

(PS: You're talking about Ubuntu, please note that the testcase comes from Debian)

October 01
https://bugzilla.gdcproject.org/show_bug.cgi?id=273

Johannes Pfau <johannespfau@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |johannespfau@gmail.com

--- Comment #5 from Johannes Pfau <johannespfau@gmail.com> ---
I can't reproduce this with the latest gdc-7 branch on an Archlinux system.

Though if this is GC memory corruption it's likely even small changes in GDC/phobos or the used OS can hide such a problem :-(

-- 
You are receiving this mail because:
You are watching all bug changes.
October 01
https://bugzilla.gdcproject.org/show_bug.cgi?id=273

--- Comment #6 from Iain Buclaw <ibuclaw@gdcproject.org> ---
According to the timestamp of the gcc sources in Debian/Ubuntu, the date is it was taken was 20170502.  So that may narrow it down to a possible regression and fix commit.

-- 
You are receiving this mail because:
You are watching all bug changes.
October 01
https://bugzilla.gdcproject.org/show_bug.cgi?id=273

--- Comment #7 from Johannes Pfau <johannespfau@gmail.com> ---
OK, can reproduce with revision ac0c40aca0638ba0f22e23dd5c03da35ef4f311a.

-- 
You are receiving this mail because:
You are watching all bug changes.
October 01
https://bugzilla.gdcproject.org/show_bug.cgi?id=273

--- Comment #8 from Iain Buclaw <ibuclaw@gdcproject.org> ---
(In reply to Johannes Pfau from comment #7)
> OK, can reproduce with revision ac0c40aca0638ba0f22e23dd5c03da35ef4f311a.

Excellent.  I can only so far reproduce using f29d15a1a96856c0880aef832bf1d5859bbb1086 - after applying all debian-specific patches *and* configuring with mostly the same flags as debian's build.

If I remove the patches, then it works.

-- 
You are receiving this mail because:
You are watching all bug changes.
October 01
https://bugzilla.gdcproject.org/show_bug.cgi?id=273

--- Comment #9 from Iain Buclaw <ibuclaw@gdcproject.org> ---
So far I've narrowed it down to the commit *before* updating to 2.072 (bad) and
the commit *after* updating to 2.075 (good).

Chances am it may just be libphobos 2.071 that is bad, but will continue to dig a bit further.

-- 
You are receiving this mail because:
You are watching all bug changes.
« First   ‹ Prev
1 2