-
Notifications
You must be signed in to change notification settings - Fork 262
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
..\..\common\alloc.c:1652: sysnum_UserConnectToServer != -1 (error finding alloc syscall #) #419
Comments
From [email protected] on May 26, 2011 06:22:48 The asserting line was introduced in r290 And it has led to crashes on a number of tests https://code.google.com/p/chromium/issues/detail?id=82401 [this bug shows a regression between r273 and r293 ] Status: Started |
From [email protected] on May 26, 2011 06:48:28 Labels: -Bug-ToolCrash Bug-Assert |
From [email protected] on May 26, 2011 06:52:14 if this isn't exported then issue #388 covers a general soln |
From [email protected] on May 26, 2011 08:30:22 Looks like there's no UserConnectToServer on XP32 (in windbg on Wordpad.exe)
Maybe we should just relax this assert? |
From [email protected] on May 26, 2011 13:24:02 Owner: [email protected] |
From [email protected] on May 26, 2011 17:25:52 This issue was closed by revision r312 . Status: Fixed |
From [email protected] on May 26, 2011 09:10:05
This is net_unittests on XP32:
C:\chromium\src>tools\valgrind\chrome_tests.bat -t net --tool drmemory --tool_flags="--use_debug"
--gtest_filter="HttpAuthHandlerFactoryTest.DefaultFactory:CookieMonsterTest.TestHostGarbageCollection:HttpAuthTest.ChooseBestChallenge"
Original issue: http://code.google.com/p/drmemory/issues/detail?id=419
The text was updated successfully, but these errors were encountered: