Skip to content
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

UNADDR in RtlInitializeCriticalSectionEx on every win7 app #301

Closed
derekbruening opened this issue Nov 28, 2014 · 3 comments
Closed

UNADDR in RtlInitializeCriticalSectionEx on every win7 app #301

derekbruening opened this issue Nov 28, 2014 · 3 comments

Comments

@derekbruening
Copy link
Contributor

From bruen...@google.com on February 17, 2011 18:49:03

every test on win7 buildbot has extra unaddr, and I'm seeing this on my
laptop now (wasn't before: not sure whether recent DR changes tweaked
something):

Error #1: UNADDRESSABLE ACCESS: writing 0x010d5980-0x010d5984 4 byte(s)
@0:00:02.312 in thread 296
Note: next higher malloc: 0x010d59a8-0x010d59c8
Note: prev lower malloc: 0x010d5948-0x010d5968
0x779e46f4 <ntdll.dll+0x346f4> ntdll.dll!RtlInitializeCriticalSectionEx
??:0
0x779e24a1 <ntdll.dll+0x324a1> ntdll.dll!RtlInitializeCriticalSectionAndSpinCount
??:0
0x77050060 <KERNELBASE.dll+0x10060> KERNELBASE.dll!InitializeCriticalSectionAndSpinCount
??:0
0x00d0a34b <hello.exe+0xa34b> hello.exe!__crtInitCritSecAndSpinCount
f:\dd\vctools\crt_bld\self_x86\crt\src\initcrit.c:86
0x00d04044 <hello.exe+0x4044> hello.exe!_ioinit
f:\dd\vctools\crt_bld\self_x86\crt\src\ioinit.c:288
0x00d01432 <hello.exe+0x1432> hello.exe!__tmainCRTStartup
f:\dd\vctools\crt_bld\self_x86\crt\src\crt0.c:235
0x75c03677 <KERNEL32.dll+0x13677> KERNEL32.dll!BaseThreadInitThunk
??:0
0x779e9d72 <ntdll.dll+0x39d72> ntdll.dll!RtlInitializeExceptionChain
??:0
0x779e9d45 <ntdll.dll+0x39d45> ntdll.dll!RtlInitializeExceptionChain
??:0

Original issue: http://code.google.com/p/drmemory/issues/detail?id=301

@derekbruening
Copy link
Contributor Author

From bruen...@google.com on February 23, 2011 08:15:13

the issue here is that a recursive heap call goes off on a tangential sequence of heap actions (here, for "heap maintenance") that are all ignored by my recursive-is-a-helper assumptions. this may also explain issue #37 and issue #21 .

@derekbruening
Copy link
Contributor Author

From bruen...@google.com on February 23, 2011 20:34:14

this unaddr looks like the one in issue #64

@derekbruening
Copy link
Contributor Author

From derek.br...@gmail.com on February 24, 2011 21:15:57

This issue was closed by revision r190 .

Status: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant