D
Dan
When I use WinDBG to analyze a crash which occurs in VB6, I get the
following extremely annoying warning:
WARNING: symbols timestamp is wrong 0x39a17cb5 0x358b0c74 for VBA6.dll
I know that I've got VBA6.DBG in my NT_SYMBOLS_PATH; and I'm also sure that
I got it off of the original VB6 setup disks (where it's hidden on disk 3).
However, the service packs have not included VBA6.DBG (they have
MSVBVM60.DBG and OLEAUT32.DBG). Why is this??!!!!!
And why are the VB symbols files not on the symbols server? It's hard
enough to develop in this environment--but it's ridiculous that you can't
get up-to-date symbols for such fundamental DLLs.
Can someone explain to me why this is--or better yet, point me somewhere to
find the correct symbols?
Sorry to rant--but this was just the last straw. I have also been trying
unsuccessfully for over a year to get symbols to debug crashes which occur
in the Office VBA environment.
Dan
following extremely annoying warning:
WARNING: symbols timestamp is wrong 0x39a17cb5 0x358b0c74 for VBA6.dll
I know that I've got VBA6.DBG in my NT_SYMBOLS_PATH; and I'm also sure that
I got it off of the original VB6 setup disks (where it's hidden on disk 3).
However, the service packs have not included VBA6.DBG (they have
MSVBVM60.DBG and OLEAUT32.DBG). Why is this??!!!!!
And why are the VB symbols files not on the symbols server? It's hard
enough to develop in this environment--but it's ridiculous that you can't
get up-to-date symbols for such fundamental DLLs.
Can someone explain to me why this is--or better yet, point me somewhere to
find the correct symbols?
Sorry to rant--but this was just the last straw. I have also been trying
unsuccessfully for over a year to get symbols to debug crashes which occur
in the Office VBA environment.
Dan