Log in

View Full Version : Setting bpx __vba breakpoints


InOverMyHead
February 14th, 2001, 09:20
I have checked that the following lines are enabled as needed in Softice (I don't enabled both at the same time):
EXP=c:\windows\system\msvbvm50.dll
EXP=c:\windows\system\msvbvm60.dll

As an example when I try to set bpx __vbastrcmp I get:
Symbol not defined (__VBASTRCMP)

I can not set a bpx on any of the VB functions. I have checked in:
c:\windows\system\ and I have both dll's present.

I have no problems setting any other bpx's - only those associated with msvbvm50.dll or msvbvm60.dll when I have them enabled in winice.dat.

I feel that I am doing something very elementary wrong, but don't know where to look.

Thanks in advance

Brtascher
February 15th, 2001, 15:22
Are you paying attention to the double underscore?

Are the msvbvm60.dll in windows/system the correct full version? Some time ago an idiotic shareware overwrote my msvb....dll file. Decompile the dlls and make sure that they export the __vba function(s) you are BPXing on.
Try loading the .dll manually using the Numega symbol loader.

InOverMyHead
February 16th, 2001, 00:27
I manually loaded the exports as suggested and the bpx's now work fine.

Question: Is this the "standard" way of getting these dll's to work or do I have something set wrong?

Thanks for the tips!!!

Bratsch
February 16th, 2001, 01:01
Quote:
InOverMyHead (02-15-2001 13:27):
I manually loaded the exports as suggested and the bpx's now work fine.

Question: Is this the "standard" way of getting these dll's to work or do I have something set wrong?

Thanks for the tips!!!

I have been where you are, just so many months ago that I could only vaguely remembered the solution I employed.
Now it has come back to my old and alcohol embeded neurons ;P.
Goes like this:
Sice does not complain if the libraries you typed in winice.dat do not exist. It simply skip them from loading. a MINIMAL typing error, even an extra space in the path to the libraries is sufficient for softIce to miss them. When you do it using the symbol loader, is a "modern day" point and click process, so Windows takes care of our sloppyness. If you carefully review the spelling, path, etc in winice.dat, you will eventually get it right and the VB libraries will be loaded at boot time to softIce. DO YOU REALLY NEED IT SO?
that is the question