Bug 3461 – Unittests and assert don't work at all (Mac D1 only)

Status
RESOLVED
Resolution
WORKSFORME
Severity
regression
Priority
P2
Component
dmd
Product
D
Version
D1 (retired)
Platform
x86
OS
Mac OS X
Creation time
2009-10-31T14:43:00Z
Last change time
2014-04-18T09:12:04Z
Keywords
wrong-code
Assigned to
nobody
Creator
uewyrwie

Comments

Comment #0 by uewyrwie — 2009-10-31T14:43:31Z
Executables compiled with dmd -unittest don't run unit tests at all. assert() is checked at compile time (i.e. assert(0) triggers warnings about unreachable code), but has no effect at run time (tried compiling with -debug). Both 1.050 and 1.048 fail on Snow Leopard (32-bit kernel mode). 2.035 with same code, same switches runs the tests.
Comment #1 by clugdbug — 2010-06-24T00:43:21Z
Can somebody please check if this bug is still valid? It's hard to believe that anyone could be using DMD1 on OSX if this still applies. If it still fails, is it really a regression? Was there ever a version of D1 where it worked?
Comment #2 by clugdbug — 2010-08-09T06:11:46Z
Fawzi has confirmed this is still current. Bug 2726 seems to be the root cause.
Comment #3 by braddr — 2011-02-06T15:39:33Z
Mass migration of bugs marked as x86-64 to just x86. The platform run on isn't what's relevant, it's if the app is a 32 or 64 bit app.
Comment #4 by bugzilla — 2012-01-31T19:16:35Z
The following program: import std.stdio; unittest { writefln("in unittest"); } void main() { writefln("in main()"); } compiled with: dmd foo -unittest prints: in unittest in main()