I don't have Visual Objects. Can I still use GoVest!
GoVest! is a general Win32 debugger, meaning that GoVest! can debug any PE executable at disassembly level. If the executable contains COFF or PDB information, you should also be able to see the corresponding source lines along with the disassembly. So if you don't have Visual Objects installed, just use the standard version (GoVest.EXE) or download the Visual Objects Trial Version.

I have a C executable with PDB debug information. But I can't see the source. Why is that?
GoVest! uses IMAGEHLP.DLL to display the source information for PDB. IMAGEHELP has this capability beginning with Windows NT 5 / 2000. Older version don't support this. Check out John Robbins Bugslayer page for more info on this one.

All my executables break somewhere at startup. But I didn't put any INT 3 in there. How come?
There is a break inside the OS loader code. In some newer version of GoVest! you'll have the option to skip this automatically.

I'm trying to use the VO version, but can't see the source code. What's wrong?
There are two issues to be aware of:

1. To see the VO source you need to run GoVest! against VO's DBG files. These are generated whenever you run an application within the VO IDE. GoVest! also needs the application's VOM file to get the source line information. VOM files are only generated, if debug information is switched on for the app. Running GoVest! on VO executables (.EXE) works as well, but you will not see any source in this case.

2. You have to shut down the Visual Objects IDE before you can use GoVest!. This is because GoVest! is using CAVOADAM, which can only be initialized once. If you don't close down the Visual Objects IDE, GoVest! can't show the VO source. A corresponding message will be shown in the GoVest! status pane.

You also might be trying to use it with VO 2.0 and a machine with two VO installations. See the next question.

Can I use GoVest! with Visual Objects 2.0?
Yes, you can use both versions. If you use the VO version, make sure that the 2.0 BIN directory is first in you path, so that GoVest! can pick up CAVOADAM, CAVOATOM etc. from there and is accessing the 2.0 repository. Make sure to change the path order again, if you want to debug your 2.5 apps.

I'm using the VO version. Can GoVest! corrupt my repository?
Excellent question! The answer is: No, in general. GoVest! uses only read access functions of CAVOADAM to display the VO source. BUT, because GoVest! is a debugger giving you low level access to the system, there might be a situation, where a corruption can happen. However I haven't seen this so far.

I'm using the VO version and have INT 3 breaks over the place. What's that?
That's normal. VO puts an INT 3 at the beginning of each entity. If you want to skip these use Debug|Ignore Hard Breaks. Then, GoVest! will only stop at breakpoints set withing GoVest!

I got the source from you and found two AEF files in the ZIP. What can I do with it?
AEF files stands for Applicaiton Export File and is the way Visual Objects applications are exported from and transfered between repositories - the Visual Objects database holding the source, the object code etc. You would need to install Visual Objects on your machine to read them. A trial version, which is gould enough to give GoVest! a test run, can be found here.

I like these detachable tab pages and would like use this in my own apps. Can I?
Check out the GoVest! source.

Wouldn't it be nice to have the GoVest! integrated in the VO IDE, e.g. as subsystem.
Sure, that would be nice.

Where does the name GoVest! come from?
This story is told here.

Do I have to wear a debug vest when using GoVest! ?
While we've heard about people, who are using GoVest! without proper protection, we certainly cannot recommend this.

Where do I get an answer for a question not listed in the FAQ?
You get it here.