|
|
|
date: Sat, 24 Feb 2007 09:21:05 -0800,
group: microsoft.public.win32.programmer.tools
back
AppVerifier and WinDbg with VB6 are killing me!
Hi all,
This is the first time I post here. Recently I have been working on a
frustrating test on our VB6 application using AppVerifier and WinDbg for 2
whole days, and now I am so lost! Helpfully I can get some hints here.
Background:
Our company is going to send the software product to VeriTest for testing.
My work is to perform testing before sending it to VeriTest. I am a new guy
in this company and got started to use AppVerifier and WinDbg just a couple
of days ago.
Symptom:
Our software program seems working fine without AppVerifier. But as soon as
using AppVerifier, every time I exit the program, an exception window coming
up. Using WinDbg, I found there is a "invalid TLS index" exception at the
exit time. (Sorry I cannot post the related information right now until
Monday)
Our program is a VB6 application, using 4 timers at the beginning. After I
removed these 4 timers, there is no exception if I exit the application right
after I get in. But if I leave the application running there for a while,
about 12 minutes, (just leave there, doing nothing) then I click exit button,
the exception came up again! I have been struggling with this for a couple of
days already, really cannot figure out what causes the problem.
Question:
1. Is this exception caught by AppVerifier a real bug? Why it doesn't show
up without AppVerifier?
2. This is a VB6 application, and I am new to VB as well. (I am a VC guy)
AppVerifier can only work with executable file, so debugging costs me lots of
time because I have create a .exe file every time I test, and I really cannot
debug into the code which causes the problem.
Is there any better way to do this? (I saw another guy's post quite a while
ago, seems like he can track down to the code which causes the program. I
don't know how he could make it.)
Thanks a lot for reading this. I really appreciate your help.
date: Sat, 24 Feb 2007 09:21:05 -0800
author: Jianke
RE: AppVerifier and WinDbg with VB6 are killing me!
Hi,
Since you are using VB6, I assume this is all native code. The error you are
seeing is an error in your app or the run time caught by AppVerifier. When
the error happens, you can check the call stack (kb command in windbg) to see
where the invalid TLS index is being used. AppVerifier ships with help
documentation that can provide more information about the type of error you
are seeing. Here's the info on the error you are seeing:
Application Verifier break message
Invalid TLS index used in current stack (use kb).
Probable cause
This stop is generated if the function on the top of the stack passed an
invalid TLS index to TLS system routines. Using the kb command will reveal
the problem. The typical issue here is to assume a certain value for a TLS
index instead of calling TlsAlloc. This can happen either by thinking that
you always get value N therefore there is no need to call TlsAlloc or more
frequently due to an un-initialized variable. Invalid TLS index used in
current stack.
Information displayed by Application Verifier
Parameter1 - Invalid TLS Index
Parameter2 - Expected lower part of the index
Parameter3 - Not used
Parameter4 - Not used
Description - Invalid TLS index used in current stack (use kb)
Additional information
Verifier stop code 0351.
Please let us know if you need any further help.
Thanks,
Prasad
"Jianke" wrote:
> Hi all,
>
> This is the first time I post here. Recently I have been working on a
> frustrating test on our VB6 application using AppVerifier and WinDbg for 2
> whole days, and now I am so lost! Helpfully I can get some hints here.
>
> Background:
> Our company is going to send the software product to VeriTest for testing.
> My work is to perform testing before sending it to VeriTest. I am a new guy
> in this company and got started to use AppVerifier and WinDbg just a couple
> of days ago.
>
> Symptom:
> Our software program seems working fine without AppVerifier. But as soon as
> using AppVerifier, every time I exit the program, an exception window coming
> up. Using WinDbg, I found there is a "invalid TLS index" exception at the
> exit time. (Sorry I cannot post the related information right now until
> Monday)
> Our program is a VB6 application, using 4 timers at the beginning. After I
> removed these 4 timers, there is no exception if I exit the application right
> after I get in. But if I leave the application running there for a while,
> about 12 minutes, (just leave there, doing nothing) then I click exit button,
> the exception came up again! I have been struggling with this for a couple of
> days already, really cannot figure out what causes the problem.
>
> Question:
> 1. Is this exception caught by AppVerifier a real bug? Why it doesn't show
> up without AppVerifier?
> 2. This is a VB6 application, and I am new to VB as well. (I am a VC guy)
> AppVerifier can only work with executable file, so debugging costs me lots of
> time because I have create a .exe file every time I test, and I really cannot
> debug into the code which causes the problem.
> Is there any better way to do this? (I saw another guy's post quite a while
> ago, seems like he can track down to the code which causes the program. I
> don't know how he could make it.)
>
> Thanks a lot for reading this. I really appreciate your help.
>
date: Mon, 26 Feb 2007 09:45:12 -0800
author: Prasad Kakulamarri [MSFT]
RE: AppVerifier and WinDbg with VB6 are killing me!
Hi Jianke,
Microsoft Product Support may be able to give you a hotfix for XP for the
issue you are experiencing.
Thanks,
Prasad
"Jianke" wrote:
> Thanks a lot for your efforts, Prasad!
> But do you think it works if contact Microsoft Product Support? What they
> can do?
> Can they convince Vertest folks that's not our program's problem? :)
>
> "Prasad Kakulamarri [MSFT]" wrote:
>
> > Hi Jianke,
> > I am not sure how you can convince the Veritest folks other than sending
> > them this email or proving that your app works by testing it on Vista. You
> > can also contact Microsoft Product Support and they may be able to help you.
> > Thank you,
> > Prasad
> >
> > "Jianke" wrote:
> >
> > > Hi Prasad,
> > >
> > > The person working for VeriTest replied, "Considering the sheer number of
> > > tests that we conduct on XP, I cant imagine that we would have a critical
> > > error caused by a bug on that platform."
> > >
> > > How do you think about this?
> > >
> > > Thanks a lot for your help.
> > >
> > > Jianke
> > >
> > > "Prasad Kakulamarri [MSFT]" wrote:
> > >
> > > >
> > > > Hi,
> > > > This is a bug in MFC and it should be fixed in Vista. Can you disable TLS
> > > > checks on your app to make progress on your tests or test it on Vista?
> > > > Thanks,
> > > > Prasad
> > > >
date: Thu, 1 Mar 2007 15:48:13 -0800
author: Prasad Kakulamarri [MSFT]
|
|
