Prev: How to incorporate voice commands into a VB6 application on XP?
Next: Compiled Code and Virus False Positives
From: Bee on 10 Apr 2010 18:01
Editing then CRASH!
Error message said the just in time debugger could not be found.
Sorry, i was so pissed at losing all my edits I forgot to write down the
error code.
It said something about enabing JITD in Tools but i cannot find anything in
IDE Tools.
I opened my main project and found many missing lines that I had just entered.

(1) what the heck is this all about?
(2) is there a just in time debugger?
(3) is there an AddIn that does automatic periodic saves?

I had three IDEs open trying to edit my main app and several Ax EXEs.
Did that have anything to do with it?
When the error occured all the IDEs locked up.
When I clicked 'OK' of the error message the main app IDE closed and I got
control back on the other AX IDEs.

I searched MSDN but only found just in time debugger stuff regarding C++
I have MZTools but I do not find automatic saves as part of that.

Suggestions please.

From: MikeD on 10 Apr 2010 20:20


"Bee" <Bee(a)discussions.microsoft.com> wrote in message
news:3014C16F-6D8B-4BCD-9AE6-18D6FC17025A(a)microsoft.com...
> Editing then CRASH!
> Error message said the just in time debugger could not be found.
> Sorry, i was so pissed at losing all my edits I forgot to write down the
> error code.
> It said something about enabing JITD in Tools but i cannot find anything
> in
> IDE Tools.
> I opened my main project and found many missing lines that I had just
> entered.
>
> (1) what the heck is this all about?
> (2) is there a just in time debugger?
> (3) is there an AddIn that does automatic periodic saves?
>
> I had three IDEs open trying to edit my main app and several Ax EXEs.
> Did that have anything to do with it?
> When the error occured all the IDEs locked up.
> When I clicked 'OK' of the error message the main app IDE closed and I got
> control back on the other AX IDEs.
>
> I searched MSDN but only found just in time debugger stuff regarding C++
> I have MZTools but I do not find automatic saves as part of that.
>
> Suggestions please.

There really are no suggestions we can give you other than to save often.
Unless you can provide steps to reproduce the crash, we really can't tell
you anything.

It's likely this will happen again eventually. You're especially likely to
crash the IDE if you're doing subclassing or hooking. You can also cause the
IDE to crash by not releasing window handles or DC handles that you've
created with API functions. But even if you never do those things, the IDE
can, and will, occasionally crash. I probably crash it once a day or at the
very least a few times a week.

So again: Save Often! I suggest you go into VB's Options dialog and enable
the option to save when run or prompt to save when run (I always go with the
latter because there are times I DON'T want to save). If you don't want to
do that for some unknown reason, it's not that hard to click the Save button
on the toolbar. There might be an addin that automatically saves at
intervals, but I don't know of any...and IMO, they're not necessary with the
options VB gives you to save a project when you run it.

As far as the JIT debugger, all later versions of Windows will give you this
choice for most apps if they crash, but you have to have one installed. VS++
6.0 installs one and I believe any .NET development product installs one. I
don't think any version of Windows includes a JIT debugger itself. It just
gives you the ability to debug in one if there is one. But I think you get
the choice to debug even if there's not one installed. That might explain
the message you got.

--
Mike



From: ralph on 11 Apr 2010 11:53
On Sat, 10 Apr 2010 15:01:02 -0700, Bee
<Bee(a)discussions.microsoft.com> wrote:


>(2) is there a just in time debugger?

Dr. Watson was supplied all versions of Windows until Vista. It was
replaced with "Problem Reports and Solutions".
(http://windows.microsoft.com/en-US/windows-vista/What-happened-to-Dr-Watson)

Dr. Watson was considered too 'geekish' for normal users.

If using XP or below it probably wasn't instrumented. Open Windows
Help (off the Start) and search for Dr. Watson for instructions.

For Vista and Win7 you should either use the VC++ debugger, or better
download WinDbg and install it as a JIT.
(http://www.microsoft.com/whdc/devtools/debugging/installx86.Mspx)

(The .Nxt Framework also has a JIT, but it is essentially useless for
VB programs.)

The nice thing about WinDbg is while the install is large, it is
basically non-intrusive compared to other development platforms, so it
can also be safely installed on 'production' boxes. It can also be
used to debug drivers and kernal components, not just applications.
IMHO no developer should leave home without it. <g>

-ralph
From: MikeD on 11 Apr 2010 12:38


"ralph" <nt_consulting64(a)yahoo.net> wrote in message
news:qbr3s5durm0b0n5seukptkl9jcts3h64j5(a)4ax.com...
> On Sat, 10 Apr 2010 15:01:02 -0700, Bee
> <Bee(a)discussions.microsoft.com> wrote:
>
>
>>(2) is there a just in time debugger?
>
> Dr. Watson was supplied all versions of Windows until Vista. It was
> replaced with "Problem Reports and Solutions".
> (http://windows.microsoft.com/en-US/windows-vista/What-happened-to-Dr-Watson)
>
> Dr. Watson was considered too 'geekish' for normal users.


I never considered Dr. Watson to be a JIT debugger or any kind of debugger
for that matter. <g>

--
Mike


From: ralph on 11 Apr 2010 16:57
On Sun, 11 Apr 2010 12:38:52 -0400, "MikeD" <nobody(a)nowhere.edu>
wrote:

>
>
>"ralph" <nt_consulting64(a)yahoo.net> wrote in message
>news:qbr3s5durm0b0n5seukptkl9jcts3h64j5(a)4ax.com...
>> On Sat, 10 Apr 2010 15:01:02 -0700, Bee
>> <Bee(a)discussions.microsoft.com> wrote:
>>
>>
>>>(2) is there a just in time debugger?
>>
>> Dr. Watson was supplied all versions of Windows until Vista. It was
>> replaced with "Problem Reports and Solutions".
>> (http://windows.microsoft.com/en-US/windows-vista/What-happened-to-Dr-Watson)
>>
>> Dr. Watson was considered too 'geekish' for normal users.
>
>
>I never considered Dr. Watson to be a JIT debugger or any kind of debugger
>for that matter. <g>

That's a pity. You have likely wasted a lot of time in the past. <g>

For others that may be interested in saving time in resolving Runtime
errors using a JIT Debugger ...

1. Start Registry Editor and locate the following Registry subkey in
the HKEY_LOCAL_MACHINE subtree:

\SOFTWARE\MICROSOFT\WINDOWS NT\CURRENTVERSION\AEDEBUG

2. Select the Debugger value.
3. On the Edit menu, click String.

� To use the Windows Debugger, type windbg -p %ld -e %ld.
� To use Visual C++ 4.2 or earlier, type msvc -p %ld -e %ld.
� To use Visual C++ 5.0 or later, type msdev.exe -p %ld -e %ld.
� To use .Nxt 2005 or later, type vsjitdebugger.exe -p %ld -e %ld
� To use Dr. Watson, type drwtsn32.exe -p %ld -e %ld.
You can also make Dr. Watson the default debugger by running the
command: "drwtsn32.exe -i" on Windows XP or lower.

4. Choose OK and exit Registry Editor.

The new JIT debugger is used the next time you log on.
 |  Next  |  Last
Pages: 1 2
Prev: How to incorporate voice commands into a VB6 application on XP?
Next: Compiled Code and Virus False Positives