http://d.puremagic.com/issues/show_bug.cgi?id=3884
Matti Niemenmaa <matti.niemenmaa+dbugzi...@iki.fi> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords|ice-on-valid-code |ice-on-invalid-code Summary|Segfault: typedef present |Segfault: defining a |when passing array in tuple |typedef with an invalid |argument to function |object.d |template | --- Comment #2 from Matti Niemenmaa <matti.niemenmaa+dbugzi...@iki.fi> 2010-03-11 02:34:40 PST --- Took me a while to reproduce it again myself. It's quite different from what I reported: I had an invalid object.d in the working directory, which triggers it. It seems the typedef alone is enough, the array and tuple business is unneeded: $ cat arst.d typedef int X; $ dmd -c arst.d [no errors] $ touch object.d $ dmd -c arst.d E: Child terminated by signal ‘Segmentation fault’ -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: -------