You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The two unittests tcmalloc_minimal_unittest-static and tcmalloc_minimal_unittest crashed
when I'm running it in release mode. Dedug mode is OK.
tcmalloc_minimal_unittest:
console output:
Testing empty allocation
Testing STL use
Sanity-testing all the memory allocation functions
Check failed: g_NewHook_calls > 0
crashed code line: tcmalloc_unittest.cc::1069 VerifyDeleteHookWasCalled();
tcmalloc_minimal_unittest-static:
console output:
Testing empty allocation
Testing STL use
Sanity-testing all the memory allocation functions
Check failed: g_NewHook_calls > 0
crashed code line: crtexe.c::555 mainret = main(argc, argv, envp);
additional information:
gperftools: version 2.0
OS: Windows XP SP3
Compiler: Visaul Studio 2010 Ultimate (version 10.0.30319.1)
Reported by LayzerAr on 2012-04-20 03:15:01
The text was updated successfully, but these errors were encountered:
There seems to be a number of issues with gperftools showing up on windows running VS2010.
Unfortunately, the community of users running windows are fairly reluctant to participate
in patch work and I do not have any experience with windows based software development.
So unless someone in the windows community is compelled to contribute back to the project
this is likely to stay broken for awhile.
The VS2010 compiler optimises the greater than zero test out - fix the issue by changing
line 728 of tcmalloc_unittest.cc like so:
From
static int g_##hook_type##_calls = 0; \
to
static volatile int g_##hook_type##_calls = 0; \
Regards
Andrew Haslam
Reported by ahaslam@iostack.com on 2012-07-01 23:17:50
r198 | chappedm@gmail.com | 2013-03-10 21:35:37 -0400 (Sun, 10 Mar 2013) | 5 lines
issue-425: Fixed tcmalloc unittest crashes for windows builds
Missing use of volatile was causing vs2010 to perform unwanted
optimization resulting in the crash. See issue for more details.
Originally reported on Google Code with ID 425
Reported by
LayzerAr
on 2012-04-20 03:15:01The text was updated successfully, but these errors were encountered: