Prev: Custom CEdit Text Control
Next: CTreeCtrl::SelectItem() behaves weird on VISTA
From: Joseph M. Newcomer on 25 May 2007 09:17
See below...
On Fri, 25 May 2007 14:35:02 +0200, "Thomas Minor" <Thomas.Minor(a)newsgroup.nospam> wrote:

>Hi @all,
>
>of caouse you want to see some more information an I think I have some now.
>
>First of all, I'm quite confident that there might be some buffer overruns
>and some
>resource leaks, but we're on that problem. Nevertheless the software should
>not
>crash that way.
****
These statements are inconsistent. If there are buffer overruns, then the program is free
to crash any way it feels like.
****
>The same binaries run without any crashes on Windows XP SP2.
>So that lead me to a Vista related issue. Another issue is, that we are
>talking about
>a non deterministic error which not reliable reproducable.
****
Example: on Vista, a path might be different from the path on XP. E.g., the expansion of
My Documents. This may lead to a different memory overrun pattern. If you have the
slightest suspicion of the possibility of buffer overruns, then all bets are off, the
program is broken, and trying to figure out anything until such potential buffer overruns
are identified and made safe is probably a waste of effort.
*****
>
>Here is the problem signature, we're dealing with an access violation...
>
>Problemsignatur:
> Problemereignisname: APPCRASH
> Anwendungsname: Telectrl.exe
> Anwendungsversion: 4.3.0.0
> Anwendungszeitstempel: 4656c8af
> Fehlermodulname: ntdll.dll
> Fehlermodulversion: 6.0.6000.16386
> Fehlermodulzeitstempel: 4549bdc9
> Ausnahmecode: c0000005
> Ausnahmeoffset: 0003d5d4
> Betriebsystemversion: 6.0.6000.2.0.0.256.6
> Gebietsschema-ID: 1031
> Zusatzinformation 1: b8f3
> Zusatzinformation 2: c7797676e2dfe14e940d5c80c4d40634
> Zusatzinformation 3: 0948
> Zusatzinformation 4: 68dba24590a88de4f5fa25f4ca0ac49e
>
>And here the stack trace
>
> # ChildEBP RetAddr Args to Child
>WARNING: Stack unwind information not available. Following frames may be
>wrong.
>00 0012ce78 77df18c3 01109820 010face8 00000000
>ntdll!RtlTryEnterCriticalSection+0x7a0
>01 0012ce8c 77f37a7e 012d0000 00000000 01109818 ntdll!RtlFreeHeap+0x7a
>02 0012cea0 700b4c39 012d0000 00000000 01109820 kernel32!HeapFree+0x14
****
Right here this is screaming "MEMORY DAMAGE! MEMORY DAMAGE!" and I'd be deeply suspect of
the basic code integrity.

Try running with App Verifier.

I'd suggest adding an OnIdle handler to your CWinAPp class and in it doing an
ASSERT(_heapchk() == HEAPOK);
(check the docs for the correct spelling here of the constant). But when you see storage
allocation functions in the backtrace, it means you have storage damage.
****
>03 0012ceec 6fb06179 01109820 6faf2df9 01109820 MSVCR80!free+0xcd
>04 0012cf1c 004103a0 00000000 0012cf60 0040a690 MFC80+0x36179
>05 0012cf90 0040a4e9 011079c8 010face8 00000000 Telectrl+0x103a0
>06 0012cfa8 0040a6c2 011079c8 010face8 010face8 Telectrl+0xa4e9
>07 0012cfc4 6fb02d6c 011079c8 00000000 f2692874 Telectrl+0xa6c2
>08 0012d070 6fb027ad 00008116 011079c8 00000000 MFC80+0x32d6c
>09 0012d090 6fb01543 00008116 011079c8 00000000 MFC80+0x327ad
>0a 0012d0f8 6fb01759 00000000 0025039e 00008116 MFC80+0x31543
>0b 0012d11c 6faff883 0025039e 00008116 011079c8 MFC80+0x31759
>0c 0012d164 76a01a10 0025039e 00008116 011079c8 MFC80+0x2f883
>0d 0012d190 76a01ae8 6faff82f 0025039e 00008116 USER32!GetMessageW+0x6e
>0e 0012d208 76a0286a 00316e34 6faff82f 0025039e USER32!GetMessageW+0x146
>0f 0012d248 769ed92c 00323dc0 01335250 011079c8
>USER32!GetDesktopWindow+0x10a
>10 0012d268 00409b40 0025039e 00008116 011079c8 USER32!SendMessageA+0x49
>11 0012d284 0040aa26 00008116 011079c8 00000000 Telectrl+0x9b40
>12 0012d2dc 6fb02d6c 011079c8 00000001 f269355c Telectrl+0xaa26
>13 0012d388 6fb027ad 00008118 011079c8 00000001 MFC80+0x32d6c
>14 0012d3a8 6fb01543 00008118 011079c8 00000001 MFC80+0x327ad
>15 0012d410 6fb01759 00000000 0025039e 00008118 MFC80+0x31543
>16 0012d434 6faff883 0025039e 00008118 011079c8 MFC80+0x31759
>17 0012d47c 76a01a10 0025039e 00008118 011079c8 MFC80+0x2f883
>18 0012d4a8 76a01ae8 6faff82f 0025039e 00008118 USER32!GetMessageW+0x6e
>19 0012d520 76a0286a 00316e34 6faff82f 0025039e USER32!GetMessageW+0x146
>1a 0012d560 769ed92c 00323dc0 01335250 011079c8
>USER32!GetDesktopWindow+0x10a
>1b 0012d580 00409b40 0025039e 00008118 011079c8 USER32!SendMessageA+0x49
>1c 0012d59c 0041c0f6 00008118 011079c8 00000001 Telectrl+0x9b40
>1d 0012d66c 6fb02d6c 00000002 011079c8 f269312c Telectrl+0x1c0f6
>1e 0012d718 6fb027ad 0000c179 00000002 011079c8 MFC80+0x32d6c
>1f 0012d738 6fb01543 0000c179 00000002 011079c8 MFC80+0x327ad
>20 0012d7a0 6fb01759 00000000 002402c0 0000c179 MFC80+0x31543
>21 0012d7c4 6faff883 002402c0 0000c179 00000002 MFC80+0x31759
>22 0012d80c 76a01a10 002402c0 0000c179 00000002 MFC80+0x2f883
>23 0012d838 76a01ae8 6faff82f 002402c0 0000c179 USER32!GetMessageW+0x6e
>24 0012d8b0 76a0286a 00316e34 6faff82f 002402c0 USER32!GetMessageW+0x146
>25 0012d8f0 769ed92c 00323cd8 01323c40 00000002
>USER32!GetDesktopWindow+0x10a
>26 0012d910 00434abe 002402c0 0000c179 00000002 USER32!SendMessageA+0x49
>27 0012d94c 0043abe2 011079c8 0012d964 00000018 Telectrl+0x34abe
>28 0012da14 0043a360 00000106 0012da38 004aa044 Telectrl+0x3abe2
>29 0012fa48 004132bd 00000106 025fdf3c 0032d968 Telectrl+0x3a360
>2a 0012fbac 6fb02d6c 00000106 025fdf3c f2691c6c Telectrl+0x132bd
>2b 0012fc58 6fb027ad 00000466 00000106 025fdf3c MFC80+0x32d6c
>2c 0012fc78 6fb01543 00000466 00000106 025fdf3c MFC80+0x327ad
>2d 0012fce0 6fb01759 00000000 002402c0 00000466 MFC80+0x31543
>2e 0012fd04 6faff883 002402c0 00000466 00000106 MFC80+0x31759
>2f 0012fd4c 76a01a10 002402c0 00000466 00000106 MFC80+0x2f883
>30 0012fd78 76a01ae8 6faff82f 002402c0 00000466 USER32!GetMessageW+0x6e
>31 0012fdf0 76a01c03 00316e34 6faff82f 002402c0 USER32!GetMessageW+0x146
>32 0012fe4c 76a03656 01323cd8 00000466 00000106 USER32!GetMessageW+0x261
>33 0012fe74 77df0e6e 0012fe8c 00000018 0012ff90 USER32!OffsetRect+0x4d
>34 0012fec8 6fb37cec 00305a10 00000000 00000000
>ntdll!KiUserCallbackDispatcher+0x2e
>35 00000000 00000000 00000000 00000000 00000000 MFC80+0x67cec
>
Joseph M. Newcomer [MVP]
email: newcomer(a)flounder.com
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm
From: Tom Serface on 25 May 2007 10:39
I don't know how to tell you exactly where your problem is, but I've seen
this kind of "stuff" when I've allocated memory then used more than I asked
for. Sounds like you're on the path of finding it though. You may want to
just look for every place where you allocate memory and check its usage.
it's a tedious task, but something worth doing from time to time.

Tom

"Thomas Minor" <Thomas.Minor(a)newsgroup.nospam> wrote in message
news:er0WElsnHHA.3704(a)TK2MSFTNGP02.phx.gbl...
> Hi @all,
>
> of caouse you want to see some more information an I think I have some
> now.
>
> First of all, I'm quite confident that there might be some buffer overruns
> and some
> resource leaks, but we're on that problem. Nevertheless the software
> should not
> crash that way. The same binaries run without any crashes on Windows XP
> SP2.
> So that lead me to a Vista related issue. Another issue is, that we are
> talking about
> a non deterministic error which not reliable reproducable.
>
> Here is the problem signature, we're dealing with an access violation...
>
> Problemsignatur:
> Problemereignisname: APPCRASH
> Anwendungsname: Telectrl.exe
> Anwendungsversion: 4.3.0.0
> Anwendungszeitstempel: 4656c8af
> Fehlermodulname: ntdll.dll
> Fehlermodulversion: 6.0.6000.16386
> Fehlermodulzeitstempel: 4549bdc9
> Ausnahmecode: c0000005
> Ausnahmeoffset: 0003d5d4
> Betriebsystemversion: 6.0.6000.2.0.0.256.6
> Gebietsschema-ID: 1031
> Zusatzinformation 1: b8f3
> Zusatzinformation 2: c7797676e2dfe14e940d5c80c4d40634
> Zusatzinformation 3: 0948
> Zusatzinformation 4: 68dba24590a88de4f5fa25f4ca0ac49e
>
> And here the stack trace
>
> # ChildEBP RetAddr Args to Child
> WARNING: Stack unwind information not available. Following frames may be
> wrong.
> 00 0012ce78 77df18c3 01109820 010face8 00000000
> ntdll!RtlTryEnterCriticalSection+0x7a0
> 01 0012ce8c 77f37a7e 012d0000 00000000 01109818 ntdll!RtlFreeHeap+0x7a
> 02 0012cea0 700b4c39 012d0000 00000000 01109820 kernel32!HeapFree+0x14
> 03 0012ceec 6fb06179 01109820 6faf2df9 01109820 MSVCR80!free+0xcd
> 04 0012cf1c 004103a0 00000000 0012cf60 0040a690 MFC80+0x36179
> 05 0012cf90 0040a4e9 011079c8 010face8 00000000 Telectrl+0x103a0
> 06 0012cfa8 0040a6c2 011079c8 010face8 010face8 Telectrl+0xa4e9
> 07 0012cfc4 6fb02d6c 011079c8 00000000 f2692874 Telectrl+0xa6c2
> 08 0012d070 6fb027ad 00008116 011079c8 00000000 MFC80+0x32d6c
> 09 0012d090 6fb01543 00008116 011079c8 00000000 MFC80+0x327ad
> 0a 0012d0f8 6fb01759 00000000 0025039e 00008116 MFC80+0x31543
> 0b 0012d11c 6faff883 0025039e 00008116 011079c8 MFC80+0x31759
> 0c 0012d164 76a01a10 0025039e 00008116 011079c8 MFC80+0x2f883
> 0d 0012d190 76a01ae8 6faff82f 0025039e 00008116 USER32!GetMessageW+0x6e
> 0e 0012d208 76a0286a 00316e34 6faff82f 0025039e USER32!GetMessageW+0x146
> 0f 0012d248 769ed92c 00323dc0 01335250 011079c8
> USER32!GetDesktopWindow+0x10a
> 10 0012d268 00409b40 0025039e 00008116 011079c8 USER32!SendMessageA+0x49
> 11 0012d284 0040aa26 00008116 011079c8 00000000 Telectrl+0x9b40
> 12 0012d2dc 6fb02d6c 011079c8 00000001 f269355c Telectrl+0xaa26
> 13 0012d388 6fb027ad 00008118 011079c8 00000001 MFC80+0x32d6c
> 14 0012d3a8 6fb01543 00008118 011079c8 00000001 MFC80+0x327ad
> 15 0012d410 6fb01759 00000000 0025039e 00008118 MFC80+0x31543
> 16 0012d434 6faff883 0025039e 00008118 011079c8 MFC80+0x31759
> 17 0012d47c 76a01a10 0025039e 00008118 011079c8 MFC80+0x2f883
> 18 0012d4a8 76a01ae8 6faff82f 0025039e 00008118 USER32!GetMessageW+0x6e
> 19 0012d520 76a0286a 00316e34 6faff82f 0025039e USER32!GetMessageW+0x146
> 1a 0012d560 769ed92c 00323dc0 01335250 011079c8
> USER32!GetDesktopWindow+0x10a
> 1b 0012d580 00409b40 0025039e 00008118 011079c8 USER32!SendMessageA+0x49
> 1c 0012d59c 0041c0f6 00008118 011079c8 00000001 Telectrl+0x9b40
> 1d 0012d66c 6fb02d6c 00000002 011079c8 f269312c Telectrl+0x1c0f6
> 1e 0012d718 6fb027ad 0000c179 00000002 011079c8 MFC80+0x32d6c
> 1f 0012d738 6fb01543 0000c179 00000002 011079c8 MFC80+0x327ad
> 20 0012d7a0 6fb01759 00000000 002402c0 0000c179 MFC80+0x31543
> 21 0012d7c4 6faff883 002402c0 0000c179 00000002 MFC80+0x31759
> 22 0012d80c 76a01a10 002402c0 0000c179 00000002 MFC80+0x2f883
> 23 0012d838 76a01ae8 6faff82f 002402c0 0000c179 USER32!GetMessageW+0x6e
> 24 0012d8b0 76a0286a 00316e34 6faff82f 002402c0 USER32!GetMessageW+0x146
> 25 0012d8f0 769ed92c 00323cd8 01323c40 00000002
> USER32!GetDesktopWindow+0x10a
> 26 0012d910 00434abe 002402c0 0000c179 00000002 USER32!SendMessageA+0x49
> 27 0012d94c 0043abe2 011079c8 0012d964 00000018 Telectrl+0x34abe
> 28 0012da14 0043a360 00000106 0012da38 004aa044 Telectrl+0x3abe2
> 29 0012fa48 004132bd 00000106 025fdf3c 0032d968 Telectrl+0x3a360
> 2a 0012fbac 6fb02d6c 00000106 025fdf3c f2691c6c Telectrl+0x132bd
> 2b 0012fc58 6fb027ad 00000466 00000106 025fdf3c MFC80+0x32d6c
> 2c 0012fc78 6fb01543 00000466 00000106 025fdf3c MFC80+0x327ad
> 2d 0012fce0 6fb01759 00000000 002402c0 00000466 MFC80+0x31543
> 2e 0012fd04 6faff883 002402c0 00000466 00000106 MFC80+0x31759
> 2f 0012fd4c 76a01a10 002402c0 00000466 00000106 MFC80+0x2f883
> 30 0012fd78 76a01ae8 6faff82f 002402c0 00000466 USER32!GetMessageW+0x6e
> 31 0012fdf0 76a01c03 00316e34 6faff82f 002402c0 USER32!GetMessageW+0x146
> 32 0012fe4c 76a03656 01323cd8 00000466 00000106 USER32!GetMessageW+0x261
> 33 0012fe74 77df0e6e 0012fe8c 00000018 0012ff90 USER32!OffsetRect+0x4d
> 34 0012fec8 6fb37cec 00305a10 00000000 00000000
> ntdll!KiUserCallbackDispatcher+0x2e
> 35 00000000 00000000 00000000 00000000 00000000 MFC80+0x67cec
>

From: Charles Wang[MSFT] on 28 May 2007 04:08
Hi Thomas,
You may refer to the article in Jeffery's suggestion to try debugging your
application.
Also I would like to appreciate your understanding that since the
environment is complex and this issue is memory related which may need
memory dump analysis for further research, our managed newsgroup may not be
the best support for such issues. You may want to know our support boundary:
http://blogs.msdn.com/msdnts/archive/2006/11/08/msdn-service-introduction.as
px

In this case, effectively and immediately I recommend that you contact
Microsoft Customer Support Services (CSS) via telephone so that a dedicated
Support Professional can assist you recover the server in a more efficient
manner. Please be advised that contacting phone support will be a charged
call.

To obtain the phone numbers for specific technology request please take a
look at the web site listed below.
http://support.microsoft.com/default.aspx?scid=fh;EN-US;PHONENUMBERS

If you are outside the US please see http://support.microsoft.com for
regional support phone numbers.

Please feel free to let me know if you have any other questions or concerns.

Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications

If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.


Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
======================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================







First  |  Prev  | 
Pages: 1 2 3
Prev: Custom CEdit Text Control
Next: CTreeCtrl::SelectItem() behaves weird on VISTA