CString Format causes memory issue [MFC]

Prev: CRichEditCtrl usage
Next: What to do with First-Chance exception

From: Jen on 28 Aug 2006 21:21

David,
Thanks for your help. You are right, switching that clears up the
problems I have had with the corrupted heap block. I remember
switching to statically linked because I was having trouble on a
end-user machine. I should have thought of that! I knew I was
required to have it one way, and when it "appeared" to work statically,
I thought it was okay. Thank you!

HOWEVER, :(
I am still having the crash at the end of the program however. The
application Verifier shows an invalid TLS index. It seems to be in the
WinMainCRTStartup...What could that be?

Thank you all for your help on this...I would have been lost without
all your assistance, and I appreciate your help...
Jen

- <avrf:logfile xmlns:avrf="Application Verifier">
- <avrf:logSession TimeStarted="2006-08-28 : 21:10:40" PID="2560"
Version="1">
- <avrf:logEntry Time="2006-08-28 : 21:10:44" LayerName="TLS"
StopCode="0x352" Severity="Error">
<avrf:message>Using an invalid TLS index.</avrf:message>
<avrf:parameter1>7abba - TLS index</avrf:parameter1>
<avrf:parameter2>0 - Not Used.</avrf:parameter2>
<avrf:parameter3>0 - Not Used.</avrf:parameter3>
<avrf:parameter4>0 - Not Used.</avrf:parameter4>
- <avrf:stackTrace>
<avrf:trace>vfbasics!CheckTlsIndex+ce</avrf:trace>
<avrf:trace>vfbasics!AVrfpTlsSetValue+3b</avrf:trace>
<avrf:trace>MFC42!Ordinal2427+90</avrf:trace>
<avrf:trace>MFC42!Ordinal806+28</avrf:trace>

<avrf:trace>vrfcore!VfCoreStandardDllEntryPointRoutine+127</avrf:trace>

<avrf:trace>vfbasics!AVrfpStandardDllEntryPointRoutine+10e</avrf:trace>

<avrf:trace>ntdll!LdrInitializeThunk+29</avrf:trace>
<avrf:trace>ntdll!LdrShutdownProcess+142</avrf:trace>
<avrf:trace>kernel32!IsValidLocale+8eb</avrf:trace>
<avrf:trace>kernel32!ExitProcess+14</avrf:trace>
<avrf:trace>vfbasics!AVrfpExitProcess+3a</avrf:trace>
<avrf:trace>msvcrt!strerror+2b4b</avrf:trace>
<avrf:trace>msvcrt!initterm+111</avrf:trace>
<avrf:trace>msvcrt!exit+12</avrf:trace>
<avrf:trace>EtrackerTrends!WinMainCRTStartup+13e</avrf:trace>
<avrf:trace>kernel32!RegisterWaitForInputIdle+49</avrf:trace>
</avrf:stackTrace>
</avrf:logEntry>
</avrf:logSession>
</avrf:logfile>

From: Jen on 28 Aug 2006 21:22

From: David Ching on 28 Aug 2006 22:06

"Jen" <leonard522(a)aol.com> wrote in message
news:1156814521.858960.292730(a)m79g2000cwm.googlegroups.com...
> David,
> Thanks for your help. You are right, switching that clears up the
> problems I have had with the corrupted heap block. I remember
> switching to statically linked because I was having trouble on a
> end-user machine. I should have thought of that! I knew I was
> required to have it one way, and when it "appeared" to work statically,
> I thought it was okay. Thank you!
>

Glad it works now! :-)

> HOWEVER, :(
> I am still having the crash at the end of the program however. The
> application Verifier shows an invalid TLS index. It seems to be in the
> WinMainCRTStartup...What could that be?
>

If Verifier is like BoundsChecker, there is a gazillion false positives. I
don't think you have control over what WinMainCRTStartup does. If the app
doesn't crash on exit in normal use, I wouldn't worry about it.

-- David

First | Prev |
Pages: 1 2 3 4 5 6
Prev: CRichEditCtrl usage
Next: What to do with First-Chance exception