Re: many errors is windows DLL's, drivers DLL's etc.

222 views

Skip to first unread message

Derek Bruening

unread,

Mar 1, 2013, 10:53:25 PM3/1/13

to drmemor...@googlegroups.com

Dr. Memory is a work in progress. As the documentation says (http://drmemory.org/docs/page_release_notes.html#sec_limits), we do not yet have all the system call data needed to eliminate false positives on graphical or networked applications. If you would like to contribute to this effort please let us know.

On Fri, Mar 1, 2013 at 8:20 PM, Bram Vaessen <bram.v...@gmail.com> wrote:

MSVCP100D.dll

If this is pulled in by your own program, then you aren't following the recommendations for building your application (http://drmemory.org/docs/page_prep.html#sec_prep_windows). The Visual Studio debug features clash with Dr. Memory and it's best to avoid the debug C and C++ libraries.

atioglxx.dll
KERNELBASE.dll
USER32.dll
aticfx32.dll
OPENGL32

and more....
these errors are all sorts like UNINITIALIZED READ, UNADDRESSABLE ACCESS, LEAK, POSSIBLE LEAK etc.

We are interested in the unaddressable accesses, which are surprising. Can you file an issue with instructions on how to reproduce the unaddrs?

What am I to make of this? Is windows really this full of errors? Or can I assume these are false negatives?

Probably you mean "false positives". A false negative is an actual error that is not reported. Many of them may be false positives: we know of uninitialized read false positives in graphical and networked apps that are being worked on. What platform are you on, and what are the characteristics of your application (how large, graphical vs console, direct win32 API or C, etc.)?

Second question: isn't there a easy way to disable error checking outside the .exe file I am working on? I'm not using any custom DLL's thatI'm working myself on, and it seems kinda strange that there is no option (as far as I know) to only show errors in the executable. now it takes quite a long time before I can finally get a list of errors that are related to MY code...

Errors in an executable are often detected in library routines when the executable passes incorrect data to the library, so it's not quite so simple as looking at exactly where the error is reported. Limiting to appearing somewhere in the callstack can have issues with long callstacks that are truncated but could be done. Please file a feature request in the issue tracker (http://code.google.com/p/drmemory/issues/list) if you have something in mind

- Derek

Bram Vaessen

unread,

Mar 3, 2013, 8:19:04 AM3/3/13

to drmemor...@googlegroups.com

Thanks for your elaborate answer, I will look at the initial results again, without any suppresions (and following the gruidelines for msvc++), and have a closer look at the unadressables to see if I can reproduce them in a simple program.

Currently I'm using the openscenegraph library, and also zlib and tinythreads. My own code is in the beginning stages, but of course openscenegraph is not a 'small' library. Zlib and tinythreads could be considered small.

Also good point about the errors in dll being caused by my code, I will again look trough all the errors and see if they could be originated by my own code.

Bram

Op zaterdag 2 maart 2013 04:53:25 UTC+1 schreef Derek Bruening het volgende:

Bram Vaessen

unread,

Mar 3, 2013, 12:10:58 PM3/3/13

to drmemor...@googlegroups.com

Okay I have changed a few things, I followed the advice for msvc++ and I also had to include the releaser versions of openscenegraph to not make the program crash (why is that?)

I'm not sure what you are looking for, most errors are in the ati dll's. I used the following suppress file now:

UNINITIALIZED READ

UNADDRESSABLE ACCESS <--- lot of these

atioglxx.dll!atiPPHSN

UNADDRESSABLE ACCESS <--- lot of these

atioglxx.dll!DrvPresentBuffers

WARNING

POSSIBLE LEAK

In the suppressed errors, I did not see any reference in either my own program, or the OSG library, they just seems to 'start' in the ati dll's, or the opengl dll(S), and there were a lot of them, that's why I removed them.

Btw this is what I meant by providing an option to exclude these kind of errors by default: they do not seem to contain any information for the 'avarage' programmer like me to find the source a the bug in my own program.

Now during the program I get only one error, and only once

~~Dr.M~~

~~Dr.M~~ Error #1: UNADDRESSABLE ACCESS: reading 0x0061246b-0x00612470 5 byte(s) within 0x00612460-0x00612470

~~Dr.M~~ # 0 aticfx32.dll!AmdQueryPowerXpressDeviceInfo +0x259cf (0x7220db7f <aticfx32.dll+0x7db7f>)

~~Dr.M~~ # 1 aticfx32.dll!GetKtProcAddress +0xd7b (0x721e667c <aticfx32.dll+0x5667c>)

~~Dr.M~~ # 2 aticfx32.dll!GetKtProcAddress +0xca6 (0x721e65a7 <aticfx32.dll+0x565a7>)

~~Dr.M~~ # 3 aticfx32.dll!OpenAdapter +0x1c1d2 (0x721e4d33 <aticfx32.dll+0x54d33>)

~~Dr.M~~ # 4 atigktxx.dll!XopOpenLinkedAdapter +0x146b (0x57175956 <atigktxx.dll+0x5956>)

~~Dr.M~~ # 5 atigktxx.dll!SetThunkProxyBypassMode +0x1f0d (0x57173258 <atigktxx.dll+0x3258>)

~~Dr.M~~ # 6 atioglxx.dll!DrvPresentBuffers +0x41b1 (0x516cd712 <atioglxx.dll+0x3d712>)

~~Dr.M~~ # 7 atioglxx.dll!DrvPresentBuffers +0x9350b2 (0x51ffe613 <atioglxx.dll+0x96e613>)

~~Dr.M~~ # 8 atioglxx.dll!DrvPresentBuffers +0x8f8b99 (0x51fc20fa <atioglxx.dll+0x9320fa>)

~~Dr.M~~ # 9 atioglxx.dll!DrvPresentBuffers +0x90590 (0x51759af1 <atioglxx.dll+0xc9af1>)

~~Dr.M~~ #10 atioglxx.dll!DrvPresentBuffers +0x8c9454 (0x51f929b5 <atioglxx.dll+0x9029b5>)

~~Dr.M~~ #11 atioglxx.dll!DrvPresentBuffers +0x8c8f55 (0x51f924b6 <atioglxx.dll+0x9024b6>)

~~Dr.M~~ Note: @0:00:16.840 in thread 5948

~~Dr.M~~ Note: next higher malloc: 0x00612498-0x006124b8

~~Dr.M~~ Note: refers to 1 byte(s) beyond last valid byte in prior malloc

~~Dr.M~~ Note: prev lower malloc: 0x00612450-0x0061246b

~~Dr.M~~ Note: instruction: pcmpistri %xmm0 0xfffffff0(%eax) $0x0c -> %ecx

Then when I close the program:

Error #2: LEAK 52 direct bytes 0x006242e8-0x0062431c + 32 indirect bytes

# 0 IMM32.dll!ImmGetImeInfoEx +0xad (0x76551586 <IMM32.dll+0x11586>)

# 1 IMM32.dll!CtfImmGetTMAEFlags +0xec (0x7655247a <IMM32.dll+0x1247a>)

# 2 IMM32.dll!ImmGetContext +0x84 (0x76552109 <IMM32.dll+0x12109>)

# 3 IMM32.dll!ImmGetContext +0x18 (0x7655209d <IMM32.dll+0x1209d>)

# 4 USER32.dll!RegisterHotKey +0x3e8 (0x75d2d660 <USER32.dll+0x1d660>)

# 5 USER32.dll!PostThreadMessageW +0xcf7 (0x75d29b66 <USER32.dll+0x19b66>)

# 6 USER32.dll!GetUserObjectInformationW +0x112 (0x75d27b85 <USER32.dll+0x17b85>)

# 7 USER32.dll!GetUserObjectInformationW +0x147 (0x75d27bba <USER32.dll+0x17bba>)

# 8 USER32.dll!gapfnScSendMessage +0x26f (0x75d26238 <USER32.dll+0x16238>)

# 9 USER32.dll!gapfnScSendMessage +0x921 (0x75d268ea <USER32.dll+0x168ea>)

#10 USER32.dll!GetWindowLongW +0x189 (0x75d27177 <USER32.dll+0x17177>)

#11 USER32.dll!GetDC +0xaa (0x75d272f1 <USER32.dll+0x172f1>)

Error #3: LEAK 160 direct bytes 0x0602ab70-0x0602ac10 + 1464 indirect bytes

# 0 main [c:\world2\world2\main.cpp:131]

Error #4: LEAK 4 direct bytes 0x0c650638-0x0c65063c + 0 indirect bytes

# 0 atioglxx.dll!atiPPHSN +0x11b013 (0x52548fa4 <atioglxx.dll+0xeb8fa4>)

# 1 atioglxx.dll!atiPPHSN +0x11c7b9 (0x5254a74a <atioglxx.dll+0xeba74a>)

# 2 atioglxx.dll!DrvPresentBuffers +0x9310e9 (0x51ffa64a <atioglxx.dll+0x96a64a>)

# 3 atioglxx.dll!DrvPresentBuffers +0x908f63 (0x51fd24c4 <atioglxx.dll+0x9424c4>)

# 4 atioglxx.dll!DrvPresentBuffers +0x9096d7 (0x51fd2c38 <atioglxx.dll+0x942c38>)

# 5 atioglxx.dll!DrvPresentBuffers +0x931a8b (0x51ffafec <atioglxx.dll+0x96afec>)

# 6 atioglxx.dll!DrvPresentBuffers +0x90335f (0x51fcc8c0 <atioglxx.dll+0x93c8c0>)

# 7 atioglxx.dll!DrvPresentBuffers +0x6cdff0 (0x51d97551 <atioglxx.dll+0x707551>)

# 8 atioglxx.dll!DrvPresentBuffers +0x6f120e (0x51dba76f <atioglxx.dll+0x72a76f>)

# 9 atioglxx.dll!DrvPresentBuffers +0x6f3cb7 (0x51dbd218 <atioglxx.dll+0x72d218>)

#10 atioglxx.dll!DrvPresentBuffers +0x8de940 (0x51fa7ea1 <atioglxx.dll+0x917ea1>)

#11 atioglxx.dll!DrvPresentBuffers +0x8d4121 (0x51f9d682 <atioglxx.dll+0x90d682>)

Error #5: LEAK 4 direct bytes 0x0c650698-0x0c65069c + 0 indirect bytes

# 0 atioglxx.dll!atiPPHSN +0x11b013 (0x52548fa4 <atioglxx.dll+0xeb8fa4>)

# 1 atioglxx.dll!atiPPHSN +0x11c7b9 (0x5254a74a <atioglxx.dll+0xeba74a>)

# 2 atioglxx.dll!DrvPresentBuffers +0x9310e9 (0x51ffa64a <atioglxx.dll+0x96a64a>)

# 3 atioglxx.dll!DrvPresentBuffers +0x908f63 (0x51fd24c4 <atioglxx.dll+0x9424c4>)

# 4 atioglxx.dll!DrvPresentBuffers +0x9076e6 (0x51fd0c47 <atioglxx.dll+0x940c47>)

# 5 atioglxx.dll!DrvPresentBuffers +0x93291f (0x51ffbe80 <atioglxx.dll+0x96be80>)

# 6 atioglxx.dll!DrvPresentBuffers +0x931a23 (0x51ffaf84 <atioglxx.dll+0x96af84>)

# 7 atioglxx.dll!DrvPresentBuffers +0x9032db (0x51fcc83c <atioglxx.dll+0x93c83c>)

# 8 atioglxx.dll!DrvPresentBuffers +0x6cdfa9 (0x51d9750a <atioglxx.dll+0x70750a>)

# 9 atioglxx.dll!DrvPresentBuffers +0x6f120e (0x51dba76f <atioglxx.dll+0x72a76f>)

#10 atioglxx.dll!DrvPresentBuffers +0x6f3cb7 (0x51dbd218 <atioglxx.dll+0x72d218>)

#11 atioglxx.dll!DrvPresentBuffers +0x8de940 (0x51fa7ea1 <atioglxx.dll+0x917ea1>)

Error #6: LEAK 4 direct bytes 0x0c650878-0x0c65087c + 0 indirect bytes