Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issues when creating a debug build of druntime library #17113

Open
dlangBugzillaToGithub opened this issue Feb 14, 2011 · 0 comments
Open

Issues when creating a debug build of druntime library #17113

dlangBugzillaToGithub opened this issue Feb 14, 2011 · 0 comments

Comments

@dlangBugzillaToGithub
Copy link

Rainer Schuetze (@rainers) reported this on 2011-02-14T23:22:30Z

Transferred from https://issues.dlang.org/show_bug.cgi?id=5583

Description

Created attachment 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.

!!!There are attachements in the bugzilla issue that have not been copied over!!!

@thewilsonator thewilsonator added the Druntime Specific to druntime label Dec 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants