J
John McGhie
Hi John:
Welcome to "the blame game", otherwise known as "finger-pointing"
I agree with their comment that an application should be able to gracefully
recover. But software does not live in a perfect world. In this case, as
far as Word is concerned, it believes that it has nothing to recover "from".
It can't tell that it has hung, it simply knows that it's waiting. It's the
operating system's job to tell it that what it is waiting for is not going
to ever occur.
Just what the Microsoft developers found I don't know, other than what they
told me which is "it's not in our code". That's all they said.
Busy software developers working on the next version of a major product
don't stop around to chat. And software developers are legendary for
"answering only the question that was asked, nothing more".
Either way: All I know is that they said "It's not in our code". Chances
are, they don't know whose code the problem actually occurs in. They can
see from the dump where the program counter was pointing: so they know the
memory location in which the problem occurred. They know that their
software has nothing in that location. Chances are, they DON'T know what
software (if any..) does have something in that location.
I am sure they could find out. But they would have to spend four hours
setting things up to get that information, and it would not do them any
good, because they know it's not in their code so they know they can't do
anything about it.
But I am speculating here. We have "It's not in our code". That's twice as
good as what we usually get on these things. Usually, they simply say "We
will investigate" and I hear nothing more.
So: I can't add anything further.
Cheers
--
The email below is my business email -- Please do not email me about forum
matters unless I ask you to; or unless you intend to pay!
John McGhie, Microsoft MVP (Word, Mac Word), Consultant Technical Writer,
McGhie Information Engineering Pty Ltd
Sydney, Australia. | Ph: +61 (0)4 1209 1410 | mailto:[email protected]
Welcome to "the blame game", otherwise known as "finger-pointing"
I agree with their comment that an application should be able to gracefully
recover. But software does not live in a perfect world. In this case, as
far as Word is concerned, it believes that it has nothing to recover "from".
It can't tell that it has hung, it simply knows that it's waiting. It's the
operating system's job to tell it that what it is waiting for is not going
to ever occur.
Just what the Microsoft developers found I don't know, other than what they
told me which is "it's not in our code". That's all they said.
Busy software developers working on the next version of a major product
don't stop around to chat. And software developers are legendary for
"answering only the question that was asked, nothing more".
Either way: All I know is that they said "It's not in our code". Chances
are, they don't know whose code the problem actually occurs in. They can
see from the dump where the program counter was pointing: so they know the
memory location in which the problem occurred. They know that their
software has nothing in that location. Chances are, they DON'T know what
software (if any..) does have something in that location.
I am sure they could find out. But they would have to spend four hours
setting things up to get that information, and it would not do them any
good, because they know it's not in their code so they know they can't do
anything about it.
But I am speculating here. We have "It's not in our code". That's twice as
good as what we usually get on these things. Usually, they simply say "We
will investigate" and I hear nothing more.
So: I can't add anything further.
Cheers
--
The email below is my business email -- Please do not email me about forum
matters unless I ask you to; or unless you intend to pay!
John McGhie, Microsoft MVP (Word, Mac Word), Consultant Technical Writer,
McGhie Information Engineering Pty Ltd
Sydney, Australia. | Ph: +61 (0)4 1209 1410 | mailto:[email protected]