Bug 9660 – [meta] Not able to debug on Windows starting from ~10 MiB executable size

Status
RESOLVED
Resolution
INVALID
Severity
blocker
Priority
P2
Component
tools
Product
D
Version
D2
Platform
All
OS
Windows
Creation time
2013-03-07T04:09:00Z
Last change time
2015-06-09T04:37:41Z
Assigned to
nobody
Creator
verylonglogin.reg
Depends on
6144

Comments

Comment #0 by verylonglogin.reg — 2013-03-07T04:09:10Z
Starting from ~10 MiB executable (with debug info included) OPTLINK Issue 6144 is triggered so one have to develop further without debug info which is really pity expecially as it starts when the project is already has medium size.
Comment #1 by verylonglogin.reg — 2013-03-07T04:10:12Z
Some magic like separating a part of the project into a library may or may not help. Eliminating use of templates often helps. E.g. one should always append `.array()` after (finite) range based operations and then pass an array to a regular (non-templated) function instead of passing Voldemort types to a templated function. Another workaround is temporary commenting out some functions which uses templates (e.g. from `std.algorithm`) to debug other functions.
Comment #2 by andrej.mitrovich — 2013-03-07T18:33:01Z
Why did you open this if it's about Issue 6144? Keep issues about actual bugs and not discussions about other issues.
Comment #3 by verylonglogin.reg — 2013-03-07T21:49:14Z
(In reply to comment #2) > Why did you open this if it's about Issue 6144? Keep issues about actual bugs > and not discussions about other issues. IMHO it's a separate and valuable issue which will be fixed if Issue 6144 will but may be (probably) fixed also in a different way. Yes, fill free to mark it INVALID if you sure I'm obviously incorrect.