Cause of the crash

Hi all,
I was testing a ATL control in vb. After shutting down the control
(stopping all the activities and killing all the threads) at higher load, it
crash once the window is repainted (displaying the window after it is
overlaid by other windows). The vc debugger shows the error, that some
instructions could not be 'read'. When I analysed the stack, it showed the
following

VBA6! 0fa9174b()
VB6! 0047c9eb()

Any idea about these symbols, and how it can be interpreted. A dump of
vba.dll didn't show the address. Moreover this kind of error didn't happen
when I was testing in VC(both release and debug mode).

Thanks


--
Regards,
Mathew Joy

Onega
Fri Feb 06 07:31:41 CST 2004

try to launch the vb program in debug mode from vc. when the program crash
down, vc may give you the right context, including the exception line if you
are lucky^_^

Best wishes
Onega
www.fruitfruit.com


"Mathew Joy" <mathewjoyatxlteknologies.com> wrote in message
news:OPdhBnK7DHA.2300@TK2MSFTNGP10.phx.gbl...
> Hi all,
> I was testing a ATL control in vb. After shutting down the control
> (stopping all the activities and killing all the threads) at higher load,
it
> crash once the window is repainted (displaying the window after it is
> overlaid by other windows). The vc debugger shows the error, that some
> instructions could not be 'read'. When I analysed the stack, it showed the
> following
>
> VBA6! 0fa9174b()
> VB6! 0047c9eb()
>
> Any idea about these symbols, and how it can be interpreted. A dump of
> vba.dll didn't show the address. Moreover this kind of error didn't happen
> when I was testing in VC(both release and debug mode).
>
> Thanks
>
>
> --
> Regards,
> Mathew Joy
>
>

Igor
Fri Feb 06 11:49:34 CST 2004

"Mathew Joy" <mathewjoyatxlteknologies.com> wrote in message
news:OPdhBnK7DHA.2300@TK2MSFTNGP10.phx.gbl...
> I was testing a ATL control in vb. After shutting down the control
> (stopping all the activities and killing all the threads)

What do you mean, killing threads? You don't use TerminateThread, do
you? Can you describe the architecture of your application, and where
exactly the ActiveX control comes in?
--
With best wishes,
Igor Tandetnik

"For every complex problem, there is a solution that is simple, neat,
and wrong." H.L. Mencken

Mathew
Sat Feb 07 04:30:40 CST 2004

> What do you mean, killing threads?
I use _beginthreadex() and _endthreadex() thread to start and terminate the
thread.
> Can you describe the architecture of your application, and where
> exactly the ActiveX control comes in?
The control (invisible at runtime) is included on the vb form and is
activated when a button is clicked. The control is a server control that
uses winsock apis to accept connections from the clients. When the control
is shutdown (as explained in my previous post) at a higher load (500 clients
and 100b data sent at 10ms) by clicking another button, all the clients are
disconnected and the threads terminated. Now after this, if I click on some
other window and click back on this window (which contains only 2 buttons
and 2 list controls), I get the error and when I go into the vc debugger by
clicking cancel, I get the stack as above.

Hope I explained clearly. This doesn't happen in lower load (say 100 clients
and 100b at 10ms)

--
Regards,
Mathew Joy