How can I get the PDB files about VBE6.dll and MSO.dll?
Josen
VBE6.dll version: 6.5.10.24
MSO.dll version: 11.0.8221.0
I can't get them from MS symbol server:
http://msdl.microsoft.com/download/symbols
pat styles [microsoft]
I'd say you should track down those images first. Do you have a mini-dump
that includes them? What is you intention with these two PDBs if you don't
have matching bits to debug? Maybe I could help if I had a better
understanding of what you are trying do.
.pat styles [micorosoft]
"Josen" <Jo...@discussions.microsoft.com> wrote in message
news:65186B28-C2BB-4812...@microsoft.com...
yuhong
I don't think Office symbols were ever available to the public
anyways, that is why I don't complain about not having them. What I
usually complain about is symbols for DLLs where I suspect most of the
versions was available on the symbol server, for example older
versions of MSVBVM60.DLL had symbols available on the symbol server,
but the newer versions that comes with Vista and later don't:
SYMSRV: C:\downloads\symbols\MSVBVM60.dbg\4791A724153000\MSVBVM60.dbg
not found
SYMSRV: http://msdl.microsoft.com/download/symbols/MSVBVM60.dbg/4791A724153000/MSVBVM60.dbg
not found
SYMSRV: C:\downloads\symbols\MSVBVM60.dbg\46B100FD153000\MSVBVM60.dbg
not found
SYMSRV: http://msdl.microsoft.com/download/symbols/MSVBVM60.dbg/46B100FD153000/MSVBVM60.dbg
not found
DBGHELP: msvbvm60 - no symbols loaded
I complain about this on the Visual Basic Team Blog, and got no
response. But it took a while for the MSXML team to respond after
contacting the team using it's blog after finding that a version of
msxml4.dll that came with KB954430 had no symbols available on the
symbol server. That version still has no symbols on the symbol server,
but I now know why and the availability of a newer beta version
(MSXML4 SP3 beta) which does have symbols on the MS symbol server. For
your info, here is the SYMCHK output that shows there is no symbols
for this version of MSXML4.DLL:
DBGHELP: C:\Users\Public\msxml4-KB954430-enu\msxml4.dll - OK
SYMSRV: C:\downloads\symbols\msxml4.pdb
\F4AD0376F4EF4A10814D5F704A072BB22\msxml4.pdb not found
SYMSRV: http://msdl.microsoft.com/download/symbols/msxml4.pdb/F4AD0376F4EF4A10814D5F704A072BB22/msxml4.pdb
not found
DBGHELP: msxml4 - no symbols loaded
Anyway, right now, I am in a conversation with Agnes Zheng of MS about
missing symbols for security update MS06-057 on Windows 2000. That was
because since it was a security update, I was able to go though PSS
for free. SYMCHK output for that missing symbol:
SYMSRV: c:\downloads\symbols\comctl32.dbg\44EF137484000\comctl32.dbg
not found
SYMSRV: http://msdl.microsoft.com/download/symbols/comctl32.dbg/44EF137484000/comctl32.dbg
not found
Yuhong Bao
Josen
Thanks for you replay!
I am working on a memory leak issue about VBA programmability function in
our product.
I got some full dump files includes VBE6.dll and some UMDH logs, LeakDiag
logs.
When I analyze these files, I can't get the pdb files of VBE6.dll and MSO.dll.
Following are some segments from analyse log:
UMDH compare result:
----------------------------------------------------------------------------------------
+ 1ff80 ( 3492f - 149af) 50c allocs BackTrace8D9
+ 2e8 ( 50c - 224) BackTrace8D9 allocations
ntdll!RtlDebugAllocateHeap+000000E1
ntdll!RtlAllocateHeapSlowly+00000044
ntdll!RtlAllocateHeap+00000E64
VBE6!???+00000000 : 65002C67
+ 1800 ( 3000 - 1800) 1 allocs BackTrace13FC
ntdll!RtlDebugReAllocateHeap+000001ED
ntdll!RtlReAllocateHeap+000001DE
ole32!CRetailMalloc_Realloc+0000004B
VBE6!???+00000000 : 65006208
VBE6!???+00000000 : 6500734D
VBE6!rtcBeep+00015414
VBE6!rtcBeep+00014A41
VBE6!rtcBeep+000148E4
VBE6!rtcBeep+000152B5
---------------------------------------------------------------------------------------------
LeakDiag log:
----------------------------------------------------------------------------------------------
- <STACK numallocs="069" size="016384" totalsize="01130496">
- <STACKSTATS>
<SIZESTAT size="016384" numallocs="069" />
</STACKSTATS>
<FRAME num="0" dll="kernel32.dll" function="" filename="" line=""
addr="0x7c809b32" offset="0x00009B32" />
<FRAME num="1" dll="kernel32.dll" function="" filename="" line=""
addr="0x7c809af9" offset="0x00009AF9" />
<FRAME num="2" dll="VBE6.DLL" function="" filename="" line=""
addr="0x65008493" offset="0x00008493" />
<FRAME num="3" dll="VBE6.DLL" function="" filename="" line=""
addr="0x6500734d" offset="0x0000734D" />
<FRAME num="4" dll="VBE6.DLL" function="rtcBeep" offset="0x15414"
filename="" line="" addr="0x65063838" />
<FRAME num="5" dll="VBE6.DLL" function="rtcBeep" offset="0x14A41"
filename="" line="" addr="0x65062E65" />
<FRAME num="6" dll="VBE6.DLL" function="rtcBeep" offset="0x148E4"
filename="" line="" addr="0x65062D08" />
<STACKID>0773AB68</STACKID>
</STACK>
---------------------------------------------------------------------------------------------
So I want to know the call stack about how to alloc memory in this issue.
I got the conclusion that it is a Virtual memory leak until now.(got the
conclusion by using the debug diagnostic tool)
*******
yuhong
> missing symbols for security update MS06-057 on Windows 2000. That was
> because since it was a security update, I was able to go though PSS
> for free.
pat styles [microsoft]
Aren't those bits for MS Office? I believe that symbols for Office are not
made available to customers. You may want to confirm this with the someone
that supports Office.
.pat styles [microsoft]
"Josen" <Jo...@discussions.microsoft.com> wrote in message
news:07CFC54B-ECB3-44BA...@microsoft.com...
yuhong
<pat.sty...@microsoft.com> wrote:
> Hello Josen.
>
> Aren't those bits for MS Office? I believe that symbols for Office are not
> made available to customers.
And to my knowledge, never were made available to customers.
That is why I don't complain about not having symbols for them.
Jamey
Jamey
available? I too am trying to troubleshoot a memory leak in our VBA
prgrammability function and could really use those symbols.
pat styles [microsoft]
It would not surprise me to learn that the Office team does not make symbols
to their stuff available. However you should ask them either through a
newsgroup they monitor or directly through their support mechanism.
.pat styles [microsoft]
"Jamey" <Ja...@discussions.microsoft.com> wrote in message
news:5F42C181-4D1D-4CB6...@microsoft.com...