Reading Stack from VB6

26 Feb 2009 2:31 PM

Programmer666

If you have a problem /bug and you want to check the stack how to do that in
VB6? Can it be done without writing code?

Thanks

25 Feb 2009 5:02 PM

Ralph

"Programmer666" <programmer***@nowhere.com> wrote in message
news:go3ko2$ev2$1@news.motzarella.org...
> If you have a problem /bug and you want to check the stack how to do that
in
> VB6? Can it be done without writing code?
>
> Thanks
>

In the IDE use "Call Stack" contrl-L (Debug Menu)

If in a compiled executable use DebugBreak() and the VC++ debugger
(CodeView) or WinDbg. (or also Dr. Watson or other just-in-time debugger)

http:

25 Feb 2009 5:08 PM

Ralph

To clarify, "DebugBreak" is not an internal VB function, you have to declare
a WinAPI call:

Private Declare Sub DebugBreak Lib "kernel32" Alias "DebugBreak" ()

-ralph

25 Feb 2009 5:14 PM

Karl E. Peterson

Programmer666 wrote:

> If you have a problem /bug and you want to check the stack how to do that in
> VB6? Can it be done without writing code?

I'm curious how you got yourself in a situation, with ClassicVB, where this desire
came to be? I've been using it since the get-go, and I've never once thought that'd
help me understand my own code.

--
..NET: It's About Trust!
http://vfred.mvps.org

25 Feb 2009 5:20 PM

Ralph

"Karl E. Peterson" <k***@mvps.org> wrote in message
news:uo7vMy2lJHA.3760@TK2MSFTNGP03.phx.gbl...
> Programmer666 wrote:
> > If you have a problem /bug and you want to check the stack how to do
that in
> > VB6? Can it be done without writing code?
>
> I'm curious how you got yourself in a situation, with ClassicVB, where
this desire
> came to be? I've been using it since the get-go, and I've never once

thought that'd

> help me understand my own code.
> --

lol

This post also struck me as odd, especially since the Call Stack View is a
simple menu click. I suspect the OP is really looking for some kind of
static "call trace".

-ralph

25 Feb 2009 5:57 PM

Karl E. Peterson

Ralph wrote:
Show quoteHide quote

> "Karl E. Peterson" <k***@mvps.org> wrote...
>> Programmer666 wrote:
>> > If you have a problem /bug and you want to check the stack how to do that in
>> > VB6? Can it be done without writing code?
>>
>> I'm curious how you got yourself in a situation, with ClassicVB, where this
>> desire
>> came to be? I've been using it since the get-go, and I've never once thought
>> that'd help me understand my own code.
>
> lol
>
> This post also struck me as odd, especially since the Call Stack View is a
> simple menu click. I suspect the OP is really looking for some kind of
> static "call trace".

I was thinking more in terms of him wanting to look at pushed parameters, and such,
in addition to return addresses. Just seemed so incredibly retro, y'know?

--
..NET: It's About Trust!
http://vfred.mvps.org

26 Feb 2009 2:23 AM

Bill McCarthy

Hi,

"Programmer666" <programmer***@nowhere.com> wrote in message
news:go3ko2$ev2$1@news.motzarella.org...
> If you have a problem /bug and you want to check the stack how to do that
> in VB6? Can it be done without writing code?
>

Not from inside VB6 code as such. You have to attach an external debugger or
use the IDE.

26 Feb 2009 3:44 AM

Jason Keats

Programmer666 wrote:

> If you have a problem /bug and you want to check the stack how to do
> that in VB6? Can it be done without writing code?

I use a combination of the free add-ins HuntERR (no longer readily
available) and MZ-Tools to insert my error handlers and add line numbers.
If, or when, an error occurs I get a stack trace with line numbers - which
then gets emailed to me (if I'm not using the IDE).

So, theoretically, I don't actually write the code - just click a button to
insert a handler (of a few lines) into each sub/function.

16 Mar 2009 8:01 PM

Tony Proctor

You can do this and I have used the relevant code myself. It's particularly
useful for generating diagnostics from the field (i.e. from live customer
sites with there is no IDE or source code available) to be passed back to
Support engineers for evaluation. However, there are a few issues with the
way VB exceptions work that make it less useful than it should be

See
http://groups.google.ie/group/comp.lang.basic.visual.misc/msg/29757bfe9d9e623d?hl=en.
The original "black belt" link for the code may have moved or disappeared
after all this time but it's worth hunting around for it

Tony Proctor

Show quoteHide quote

"Programmer666" <programmer***@nowhere.com> wrote in message
news:go3ko2$ev2$1@news.motzarella.org...
> If you have a problem /bug and you want to check the stack how to do that
> in VB6? Can it be done without writing code?
>
> Thanks