Microsoft does not commit to make available symbols for all of its products.
Furthermore, it does not commit to make symbols available for all bits in
Windows. Some items are specifically held back intentionally. We do tend
to get out most symbols for major releases and the like, especially the
newer ones. This is not the case for older ones and I expect that when
debugging old releases, if the symbols are not currently available, they
probably never will be. There are also other binaries in Windows that are
produced by other teams that are not part of the the core Windows team.
These are teams such as Sustained Engineering that produce hot fixes. All
of these different teams have different policies and processes.
Because of this, I cannot recommend a contact for you to report missing
symbols. I think you need to work with what you have.
.pat styles [microsoft]
"Yuhong Bao" <yuhong...@hotmail.com> wrote in message
news:1590F845-4987-47A3...@microsoft.com...
Yuhong Bao
On Feb 11, 4:08 pm, Yuhong Bao <yuhongbao_...@hotmail.com> wrote:
> To be honest, I know who to contact to report missing MSXML symbols, for
> example, because luckily the team responsible have a blog. In fact, the only
> missing symbols I don't have a contact for reporting right now are VB6
> symbols and Windows system symbols, and I am actively trying to find a
> contact I can report these missing symbols to. I am considering the MSRC for
> missing symbols that are part of security updates, for example.
>
> "pat styles [microsoft]" wrote:
> > Hello Yuhong.
>
> > Microsoft does not commit to make available symbols for all of its products.
> > Furthermore, it does not commit to make symbols available for all bits in
> > Windows. Some items are specifically held back intentionally. We do tend
> > to get out most symbols for major releases and the like, especially the
> > newer ones. This is not the case for older ones and I expect that when
> > debugging old releases, if the symbols are not currently available, they
> > probably never will be. There are also other binaries in Windows that are
> > produced by other teams that are not part of the the core Windows team.
> > These are teams such as Sustained Engineering that produce hot fixes. All
> > of these different teams have different policies and processes.
>
> > Because of this, I cannot recommend a contact for you to report missing
> > symbols. I think you need to work with what you have.
>
> > .pat styles [microsoft]
>
> > "Yuhong Bao" <yuhongbao_...@hotmail.com> wrote in message
Do you mean that I am on my own when trying to find missing symbols?
In care you were not aware of this, Microsoft dropped support for NT4 a
while ago. This would include symbols.
http://www.microsoft.com/technet/archive/winntas/ntendlife.mspx?mfr=true
.pat styles [microsoft]
"yuhong" <yuhong...@hotmail.com> wrote in message
news:b5b60637-5d50-4b08...@x9g2000yqk.googlegroups.com...
I am afraid I would not be able to suggest anything. I believe my previous
emails were quite detailed and explain the situation quite well.
.pat styles [microsoft]
"Yuhong Bao" <yuhong...@hotmail.com> wrote in message
news:40D678AD-A450-4C91...@microsoft.com...
Yep, the missing symbols are I think from one of the last security
updates that was released before MS dropped support.
>Yep, the missing symbols are I think from one of the last security
>updates that was released before MS dropped support.
You've never really answered this question: why is it so critically
important that you get symbols for such things? For an OS where
support was dropped *years* ago? Why is it suddenly so important, now?
Nathan Mates
--
<*> Nathan Mates - personal webpage http://www.visi.com/~nathan/
# Programmer at Pandemic Studios -- http://www.pandemicstudios.com/
# NOT speaking for Pandemic Studios. "Care not what the neighbors
# think. What are the facts, and to how many decimal places?" -R.A. Heinlein
Anyway, I deleted the NT4 VM, so too late anyway.