Doug Gregor wrote:
That's very bad; CTest should be disabling this dialog, because this
is going to happen often. Unless our tests are doing something to
re-enable the dialog?
We usually use _CrtSetReportHook:
http://msdn.microsoft.com/en-us/library/0yysf5e6(VS.80).aspx
in our tests to disa
I poked around in the BuildLog.htm files (for VS2005) and build.make
files (NMake) and convinced myself that CMake builds that use the NMake
generator are specifying /RTC1, while VS 2005 builds are not.
Hmm are you building the Debug or the Release variant in VS 2005?
Perhaps this flag is o
On Sat, May 16, 2009 at 7:25 PM, David Wolfe wrote:
>> Debug Error!
>> File
>> c:\projects\boost\libs\numeric\ublas\placement_new.cpp
>> Line: 63
>>
>> Run-Time Check Failure #2 - Stack around the variable 'a' was
>> corrupted.
>
>
> On 5/16/2009 7:59 AM, Mike Jackson wrote:
>>
>> So I am goi
On Sat, May 16, 2009 at 3:57 PM, David Wolfe wrote:
>>> A runtime error in one of the unit tests has been making it difficult
>>> to get continuous builds going under Windows. I get about halfway
>>> through the tests and then a message box pops up...
>
>>> If I click 'Ignore', the rest of the te
Debug Error!
File
c:\projects\boost\libs\numeric\ublas\placement_new.cpp
Line: 63
Run-Time Check Failure #2 - Stack around the variable 'a' was
corrupted.
On 5/16/2009 7:59 AM, Mike Jackson wrote:
So I am going to assume that there is an actual bug in the code. Is it
possible to debug th
A runtime error in one of the unit tests has been making it difficult
to get continuous builds going under Windows. I get about halfway
through the tests and then a message box pops up...
If I click 'Ignore', the rest of the tests complete, and my results get
submitted to the dashboard; but th
On Fri, May 15, 2009 at 9:47 PM, David Wolfe wrote:
> A runtime error in one of the unit tests has been making it difficult to
> get continuous builds going under Windows. I get about halfway through
> the tests and then a message box pops up containing the following text:
>
> Debug Error!
>
>
I have seen that error before when I have a static array like the following:
int i[2];
and then try to access something beyond the end of the array
i[3] = 1;
I have also seen that error when doing the following:
std::vector i(0);
i[1] = 1;
So I am going to assume that there is an actual bug i
