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

More control over nvdaHelper debug builds #1390

Closed
nvaccessAuto opened this Issue Feb 24, 2011 · 1 comment

Comments

Projects
None yet
1 participant
@nvaccessAuto

nvaccessAuto commented Feb 24, 2011

Reported by jteh on 2011-02-24 06:45
It would be useful to have more control over nvdaHelper debug builds. Currently, nvdaHelperDebug=1 sets the DEBUG flag, enables assertions, provides symbols and pdbs, and uses the debug CRT. However, there are times when one wants symbols but nothing else, particularly the debug CRT, which can obscure the cause of certain crashes. We should also determine for certain whether we actually need pdbs at all, since it seems that symbols are also exported in the dlls.

@nvaccessAuto

This comment has been minimized.

nvaccessAuto commented Apr 26, 2011

Comment 1 by mdcurran on 2011-04-26 02:35
Implemented in d5706d3. the nvdaHelperDebug variable has been replaced by nvdaHelperDebugFlags, which is a comma separated list of keywords identifying which debugging options are required. Options are: symbols, assertions, debugCRT and noOptimize.
The symbols option still creates separate pdb files, there may be a way to disable this, but I feel that this is probably a different feature and does not affect the actual request of separating debugging options.
Changes:
Milestone changed from near-term to 2011.2
State: closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment