Issue 5583 - Issues when creating a debug build of druntime library
Summary: Issues when creating a debug build of druntime library
Status: NEW
Alias: None
Product: D
Classification: Unclassified
Component: druntime (show other issues)
Version: D2
Hardware: Other Windows
: P3 normal
Assignee: No Owner
URL:
Keywords: patch
Depends on:
Blocks:
 
Reported: 2011-02-14 23:22 UTC by Rainer Schuetze
Modified: 2024-12-07 13:31 UTC (History)
0 users

See Also:


Attachments
patch for issues with debug builds of druntime (2.87 KB, application/octet-stream)
2011-02-14 23:22 UTC, Rainer Schuetze
Details

Note You need to log in before you can comment on or make changes to this issue.
Description Rainer Schuetze 2011-02-14 23:22:30 UTC
Created attachment 910 [details]
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.
Comment 1 dlangBugzillaToGithub 2024-12-07 13:31:18 UTC
THIS ISSUE HAS BEEN MOVED TO GITHUB

https://github.com/dlang/dmd/issues/17113

DO NOT COMMENT HERE ANYMORE, NOBODY WILL SEE IT, THIS ISSUE HAS BEEN MOVED TO GITHUB