You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Beysim Sezgin (JIRA)" <ji...@apache.org> on 2015/10/22 01:06:27 UTC
[jira] [Comment Edited] (REEF-859) Debug c++ builds should target
retail CRT.
[ https://issues.apache.org/jira/browse/REEF-859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14967416#comment-14967416 ]
Beysim Sezgin edited comment on REEF-859 at 10/21/15 11:05 PM:
---------------------------------------------------------------
Yes, debugging the following would be better (albeit slower) with debug CRT.
- if you are using crt memory heap, then they have support for debugging memory corruption, "of by one" allocation (they allocate extra memory at the beginning and end and fill with known values and make sure they were not overwritten, etc.). Please see " C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\crt\src\dbgheap.c" for more.
- Iterator
- Concurrency runtime
- locking
- lists
- regex
- sse helpers
- ... more
But we are not really using the above (much) and can always build privates if necessary.
was (Author: beysims):
Yes, debugging the following would be better (albeit slower) with debug CRT.
- if you are using crt memory heap, then they have support for debugging memory corruption, of by one allocation (they allocate extra memory at the beginning and and fill with known values and make sure they are overwritten, etc.). Please see " C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\crt\src\dbgheap.c" for more.
- Iterator
- Concurrency runtime
- locking
- lists
- regex
- sse helpers
- ... more
But we are not really using the above (much) and can always build privates if necessary.
> Debug c++ builds should target retail CRT.
> ------------------------------------------
>
> Key: REEF-859
> URL: https://issues.apache.org/jira/browse/REEF-859
> Project: REEF
> Issue Type: Bug
> Reporter: Beysim Sezgin
>
> Currently, by default debug builds target debug CRT. I.E. msvcr120{color:red}d{color}.dll
> This dll typically would not exist on yarn clusters causing hard to debug startup issues.
> We should target retail C RunTime instead I.E. msvcr120.dll
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)