February 15, 2011 [Issue 5583] New: Issues when creating a debug build of druntime library | ||||
---|---|---|---|---|
| ||||
http://d.puremagic.com/issues/show_bug.cgi?id=5583 Summary: Issues when creating a debug build of druntime library Product: D Version: D2 Platform: Other OS/Version: Windows Status: NEW Severity: normal Priority: P2 Component: druntime AssignedTo: nobody@puremagic.com ReportedBy: r.sagitario@gmx.de --- Comment #0 from Rainer Schuetze <r.sagitario@gmx.de> 2011-02-14 23:22:30 PST --- Created an attachment (id=910) patch for issues with debug builds of druntime There are a few issues that you might hit when building a debug build of druntime. Sorry, if these issues should be in separate reports, but I did not want to bother everybody with multiple report on these non-urgent changes: 1. The GC invariants in gc.gcx are not thread safe, so I suggest to enable them only with a separate debug identifier or use one of the existing identifiers. 2. _d_arraycopy always prints debug messages, I guess this should also get some debug(PRINTF) condition. 3. _d_framehandler and _d_local_unwind assert with a range violation if they have to unwind more than entry from the handler table. This happens because the struct DHandlerTable uses a place holder array of length 1, but actually expands beyond that. The patch takes a pointer to the array to avoid the range check. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- |
Copyright © 1999-2021 by the D Language Foundation