VS2005主要开发bug [英] VS2005 major development bug
问题描述
在花了一天多的时间将一个复杂的编译器错误减少到一个简单的案例后，我把它作为一个错误报告给MSDN产品反馈中心
。然而，这个bug完全阻碍了我开发一个
VC ++组件。微软是否仍然为VS2005提供任何免费的bug报告案例
，因为他们为VS2003做了两次，这样我就可以直接与
技术代表交谈，试图找到解决方法对于
编译器错误？
虽然我通常愿意等待来自bug
报告的响应，我的代码中的错误的大小，其中编译器是生成错误的代码或者vtable在运行时被销毁时由CLR系统销毁的b / b
是这样的我死在水中，直到虫子被解决了。虽然我可以继续搜索bug的解决方法，例如，通过从托管C ++切换到C ++ / CLI来查看是否
，看看是否会导致任何更改，以便该bug不会发生，如果没有，我可以发现我必须完全放弃创建我的代码。因此，我希望
有一些方法可以直接用Microsoft
来解决这个问题，而无需直接支付它们来修复自己的错误代码。
After spending more than a day reducing a complicated compiler bug to a
simple case I reported it to the MSDN Product Feedback Center as a bug
just now. However this bug is completely stymying my development of a
VC++ component. Does Microsoft still offer any free bug reporting cases
for VS2005, as they did two for VS2003 so that I can talk with a
technical representative directly to try to find a workaround for the
compiler bug ?
While I would be normally willing to wait for a response from the bug
report, the magnitude of the bug in my code, where the compiler is
either producing wrong code or the vtable is being destroyed at run-time
by the CLR system, is such that I am dead in the water until the bug is
addressed. While I can continue searching for a workaround for the bug,
for instance by switching from Managed C++ to C++/CLI and see if that
causes any change so that the bug does not occur, if there is none I can
find I must give up creating my code entirely. Therefore I am hoping
that there is some way of addressing the problem directly with Microsoft
without having to pay them directly just to fix their own bad code.
推荐答案
Edward Diener写道：
Edward Diener wrote:
花了一天多的时间减少复杂的编译器错误
我报告的一个简单的案例它刚刚到MSDN产品反馈中心作为一个
错误。然而，这个bug完全阻碍了我对VC ++组件的开发。微软是否仍然为VS2005提供任何免费的bug报告案例，因为他们为VS2003做了两个，这样我就可以直接与技术代表交谈，试图找到编译器bug的解决方法？
虽然我通常愿意等待来自bug报告的响应，但我的代码中的bug的大小，编译器在哪里产生错误的代码或者由CLR系统在运行时销毁vtable，这样我就死在了水中，直到虫子得到解决。虽然我可以继续为bug找到解决方法，例如从托管C ++切换到C ++ / CLI
并查看是否会导致任何更改，以便不会发生错误，如果
我找不到任何东西我必须完全放弃创建我的代码。
因此我希望有一些方法可以直接与Microsoft解决问题，而无需直接付款。
只是为了修复自己的错误代码。
After spending more than a day reducing a complicated compiler bug to
a simple case I reported it to the MSDN Product Feedback Center as a
bug just now. However this bug is completely stymying my development
of a VC++ component. Does Microsoft still offer any free bug
reporting cases for VS2005, as they did two for VS2003 so that I can
talk with a technical representative directly to try to find a
workaround for the compiler bug ?
While I would be normally willing to wait for a response from the bug
report, the magnitude of the bug in my code, where the compiler is
either producing wrong code or the vtable is being destroyed at
run-time by the CLR system, is such that I am dead in the water until
the bug is addressed. While I can continue searching for a workaround
for the bug, for instance by switching from Managed C++ to C++/CLI
and see if that causes any change so that the bug does not occur, if
there is none I can find I must give up creating my code entirely.
Therefore I am hoping that there is some way of addressing the
problem directly with Microsoft without having to pay them directly
just to fix their own bad code.
支持事件通常是免费的，因为
$中的错误b $ b产品。您可能需要支付支持事件才能让事情滚动，
但我的理解是，如果确认是由于某个错误，那么他们将会支付
将退款归还给您。如果您被阻止继续，那么您需要联系PSS - 这是您获得当前
产品的修补程序的唯一方法。通过反馈中心报告错误可能会在VC ++的下一个版本中修复它，但它在短期内无法帮助你。
如果有一个小的repro case（听起来你确实开发了一个），你可以在这里发布b b b，也许有人可以帮忙找到解决方法。我假设
您的反馈FDBK48932是有问题的错误 - 如果您可以将
文件发布到新组，那么我们都可以看看。 />
-cd
There''s normally no charge for a support incident that''s due to a bug in the
product. You may have to pay for a support incident to get things rolling,
but my understanding is that if it''s confirmed to be due to a bug, they''ll
credit the charge back to you. If you''re blocked from proceeding, you
should contact PSS - that''s the only way you''ll get a hotfix to a current
product. Reporting the bug through the feedback center may get it fixed in
the next release of VC++, but it won''t help you in the short term.
If there''s a small repro case (it sounds like you did develop one) that you
could post here, perhaps someone can help find a workaround. I''m assuming
that your feedback FDBK48932 is the bug in question - if you could post the
files to the newgroup then we all could take a look.
-cd
Edward Diener写道：
Edward Diener wrote:
Carl Daniel [VC ++ MVP]写道：
Carl Daniel [VC++ MVP] wrote:
Edward Diener写道：
Edward Diener wrote:
花了一天多的时间来减少复杂的编译器错误
到一个简单的案例我把它报告给MSDN产品反馈中心一个
刚才的bug。然而，这个bug完全阻碍了我对VC ++组件的开发。微软是否仍然为VS2005提供任何免费的bug报告案例，因为他们为VS2003做了两个，这样我就可以直接与技术代表交谈，试图找到编译器bug的解决方法？
虽然我通常愿意等待来自
错误报告的响应，但我的代码中的错误的大小，编译器的位置是
要么产生错误的代码，要么vtable在运行时被CLR系统销毁，这样我就死在了水中
直到bug被解决了。虽然我可以继续为bug找到一个解决方法，例如从托管C ++切换到C ++ / CLI
并查看是否会导致任何更改，以便不会发生错误，如果没有我可以找到我必须放弃完全创建我的代码。
因此我希望有一些方法可以直接与Microsoft解决问题，而无需直接付款
只是修复自己的错误代码。
支持事件通常是免费的，这是由于产品中的错误造成的。您可能需要为支持事件支付费用才能使事情滚动，但我的理解是，如果确认是由于某个错误，他们会将这笔费用归还给您。如果你被禁止继续，你应该联系PSS - 这是你获得当前产品的修补程序的唯一方法。
After spending more than a day reducing a complicated compiler bug
to
a simple case I reported it to the MSDN Product Feedback Center as a
bug just now. However this bug is completely stymying my development
of a VC++ component. Does Microsoft still offer any free bug
reporting cases for VS2005, as they did two for VS2003 so that I can
talk with a technical representative directly to try to find a
workaround for the compiler bug ?
While I would be normally willing to wait for a response from the
bug report, the magnitude of the bug in my code, where the compiler
is
either producing wrong code or the vtable is being destroyed at
run-time by the CLR system, is such that I am dead in the water
until
the bug is addressed. While I can continue searching for a
workaround
for the bug, for instance by switching from Managed C++ to C++/CLI
and see if that causes any change so that the bug does not occur, if
there is none I can find I must give up creating my code entirely.
Therefore I am hoping that there is some way of addressing the
problem directly with Microsoft without having to pay them directly
just to fix their own bad code.
There''s normally no charge for a support incident that''s due to a
bug in the product. You may have to pay for a support incident to
get things rolling, but my understanding is that if it''s confirmed
to be due to a bug, they''ll credit the charge back to you. If
you''re blocked from proceeding, you should contact PSS - that''s the
only way you''ll get a hotfix to a current product.
<我看到了一些1-800-936-5800。这是PSS号吗？我记得
要求发生一些事件，这些事件都是针对VS2003的VC ++错误，但不记得那是否是我打过的号码。我会等待一段时间，看看是否至少可以确认该错误，然后才能通过电话路线支付微软
I see a number of 1-800-936-5800. Is that the PSS number ? I recall
calling for a number of incidents which were all VC++ bugs for VS2003
.NET but do not remember if that was the number I called. I will
probably wait a little while to see if the bug can at least be
confirmed before going the telephone route as paying Microsoft
245
我的
可能的错误在我的钱包上不容易。
245
for my
possible mistake will not be easy on my pocketbook.
转到 http://msdn.microsoft.com/support/ ，点击与Microsoft联系并且
找到您所在国家/地区的电话号码。
Go to http://msdn.microsoft.com/support/, click on "Contact Microsoft" and
find the phone number for your country.
通过反馈中心报告错误可能会在下一版VC ++中修复它但是它在短期内对你没有帮助。
我希望它能给我一个解决方法，不要对我负责
< g>。
Reporting the bug through the feedback center may get it fixed in
the next release of VC++, but it won''t help you in the short term.
I am hoping it will get me a workaround which is not to taxing on me
<g>.
如果有一个小的repro案例（听起来你确实开发了一个）
你可以发布在这里，也许有人可以帮助找到一个解决方法。我假设您的反馈FDBK48932是
问题中的错误 - 如果您可以将文件发布到新组，那么我们都可以看看。
If there''s a small repro case (it sounds like you did develop one)
that you could post here, perhaps someone can help find a
workaround. I''m assuming that your feedback FDBK48932 is the bug in
question - if you could post the files to the newgroup then we all
could take a look.
如果错误是我自己的某种方式，我会很高兴承认它。我确实花了很多时间来减少一个非常复杂的案例，一步一步，
试图用最简单的格式来说明这个bug。
I have attached the zip file to this reply which illustrates the bug
in question. I see that I had incorrectly not attached the zip file
to the FDBK48932 report and have now done so. If I am not supposed to
attach a .zip file here to this reply, please tell me which NG I
should use. The explanation for duplicating the bug is on the
FDBK48932 report.
If the bug is my own in some way I will be glad to acknowledge it. I
did spend a great deal of time reducing a very complex case, step by
step,
to try to illustrate the bug in about its simplest format.
感谢repro。今天早上我没有时间看这个，但是今晚我会花些时间在这上面。
感谢您的回复。
Thanks for the repro. I don''t have time to look at it this morning, but
I''ll spend some time on it this evening.
Thanks for your reply.
欢迎您。
-cd
You''re welcome.
-cd
这篇关于VS2005主要开发bug的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
