http://bugzilla.gdcproject.org/show_bug.cgi?id=189

--- Comment #1 from Guillaume Piolat <aliloko@gmail.com> ---
Indeed there is no unwind.d or unwind.di in those GDC releases.

-- 
You are receiving this mail because:
You are watching all bug changes.

http://bugzilla.gdcproject.org/show_bug.cgi?id=189

Tomáš Chaloupka <chalucha@gmail.com> changed:

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

-- 
You are receiving this mail because:
You are watching all bug changes.

http://bugzilla.gdcproject.org/show_bug.cgi?id=189

Johannes Pfau <johannespfau@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |johannespfau@gmail.com
           Assignee|ibuclaw@gdcproject.org      |johannespfau@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.

http://bugzilla.gdcproject.org/show_bug.cgi?id=189

Johannes Pfau <johannespfau@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ibuclaw@gdcproject.org
                 OS|MinGW                       |All
           Severity|blocker                     |major

--- Comment #2 from Johannes Pfau <johannespfau@gmail.com> ---
This is interesting:
We do not ship the unwind headers for any system but so far nobody has
complained. Just out of curiosity: can you post some example code which
triggers this error?

@Iain: I guess this is not intentional? We probably have to extend

for i in gcc; do \
=>
for i in gcc gcc/unwind; do \

in libdruntime/Makefile.am?

-- 
You are receiving this mail because:
You are watching all bug changes.

http://bugzilla.gdcproject.org/show_bug.cgi?id=189

--- Comment #3 from Iain Buclaw <ibuclaw@gdcproject.org> ---
Should be reproducible using only: import gcc.backtrace;

This would trigger for systems where the following constraints result to false: static if(BACKTRACE_SUPPORTED && !BACKTRACE_USES_MALLOC)

As libbacktrace is only really supported on Linux / similar *nix variants, that would include Mingw in the list of unsupported platforms.

-- 
You are receiving this mail because:
You are watching all bug changes.

http://bugzilla.gdcproject.org/show_bug.cgi?id=189

Johannes Pfau <johannespfau@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #4 from Johannes Pfau <johannespfau@gmail.com> ---
https://github.com/D-Programming-GDC/GDC/commit/57a6f53298b833beeb9c7e188cc2f0767098107e

I'll upload updated binary builds once I got glibc-2.14 working with gcc-5...

-- 
You are receiving this mail because:
You are watching all bug changes.