内部错误 - 如何处理错误(?)MSC#编译器? [英] INTERNAL ERROR -- how to deal with buggy (?) MSC# compiler ?

查看:66
本文介绍了内部错误 - 如何处理错误(?)MSC#编译器?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

(最初,可能是错误的,发布到vc子组。)

(这似乎不是ac#问题,但是有一个bug的问题在

Visual Studio c#编译器,但是,欢迎任何帮助......)

哦,我忘了列出错误信息;如果

有人可以解释如何推断出VC编译器无法处理的文件中的哪个行号是多少,我会很高兴。实际上我正在使用C#,但

我能找到的关于INTERNAL ERROR的唯一帖子有一个注释

说问题是vc编译器。不幸的是,它来自一年前的b $ b $并没有解决方案。当其他人遇到编译器错误时,他们会怎么做?也许你们其他人都知道如何解码这些信息

来找出哪些文件和行号混淆了编译器?


******** *****引用以下信息消息*************

内部编译器错误(地址5315C743为0xc0000005):可能是

罪魁祸首是''开始''。


编译器中发生内部错误。要解决这个问题,请尝试简化或更改下面列出的位置附近的程序

。列表顶部的位置更接近发生内部错误的点



内部编译器错误:阶段''开始''

(Was originally, probably wrongly, posted to the vc subgroup.)
(This doesn''t appear to be a c# problem, but a problem with a bug in
the Visual Studio c# compiler, but, any help will be welcome...)
Oh, I forgot to list the error messages; I would be delighted if
someone could explain how to deduce which line number in which file is
the one that the VC compiler cannot handle. Actually I''m using C#, but
the only post I could find about INTERNAL ERROR had an annotation
saying the problem is the vc compiler. Unfortunately it was from a
year ago and had no resolution. What do other people do when they hit
compiler bugs ? Perhaps you others know how to decode this information
to find out what file and line number is confusing the compiler ?

************* QUOTE INFORMATIONAL MESSAGES BELOW *************
Internal Compiler Error (0xc0000005 at address 5315C743): likely
culprit is ''BEGIN''.

An internal error has occurred in the compiler. To work around this
problem, try simplifying or changing the program near the locations
listed below. Locations at the top of the list are closer to the point
at which the internal error occurred.

Internal Compiler Error: stage ''BEGIN''

推荐答案

pe *** *********@hotmail.com (pj)写在

新闻:12 ***************** *********@posting.google.c om:
pe************@hotmail.com (pj) wrote in
news:12**************************@posting.google.c om:
(最初,可能是错误的,发布到vc子组。)
(这不是看起来似乎是ac#问题,但是Visual Studio c#编译器中有一个
错误的问题,但是,任何帮助都将受到欢迎......)

哦,我忘了列出错误信息;如果某人能够解释如何推断哪个行号是VC编译器无法处理的行号,我会很高兴。实际上我是在使用C#,但是我能找到的关于INTERNAL ERROR的唯一帖子有一个注释说问题是vc编译器。
不幸的是它是从一年前开始的没有决议。其他人在遇到编译器错误时会做些什么?也许你有其他人知道如何解码这些信息以找出哪个文件和行号混淆了编译器?

************ *引用以下信息消息*************

内部编译器错误(地址5315C743为0xc0000005):可能
罪魁祸首是开始。

编译器中发生内部错误。要解决此问题,请尝试简化或更改下面列出的位置附近的程序。列表顶部的位置更接近内部错误发生的位置。

内部编译器错误:阶段''开始''
(Was originally, probably wrongly, posted to the vc subgroup.)
(This doesn''t appear to be a c# problem, but a problem with a
bug in the Visual Studio c# compiler, but, any help will be
welcome...)
Oh, I forgot to list the error messages; I would be delighted if
someone could explain how to deduce which line number in which
file is the one that the VC compiler cannot handle. Actually I''m
using C#, but the only post I could find about INTERNAL ERROR
had an annotation saying the problem is the vc compiler.
Unfortunately it was from a year ago and had no resolution. What
do other people do when they hit compiler bugs ? Perhaps you
others know how to decode this information to find out what file
and line number is confusing the compiler ?

************* QUOTE INFORMATIONAL MESSAGES BELOW *************
Internal Compiler Error (0xc0000005 at address 5315C743): likely
culprit is ''BEGIN''.

An internal error has occurred in the compiler. To work around
this problem, try simplifying or changing the program near the
locations listed below. Locations at the top of the list are
closer to the point at which the internal error occurred.

Internal Compiler Error: stage ''BEGIN''




pj,


我从未遇到任何使用C#的内部编译器错误。想到的两个原因可能是:1)你有一些非常好的b $ b奇怪的C#代码,或者2).Net的安装在某些方面被破坏了

方式。


为了涵盖可能性#1,如果错误是可重现的,请发布一些代码

来证明问题。


对于可能性#2,您可以尝试重新安装VS.NET或SDK

(无论您使用哪一个)。我听说过挥之不去的

件的情况。测试版的VS.NET(或SDK)在安装软件的最终版本时引起了各种奇怪的问题



希望这会有所帮助。


克里斯。

-------------

CR Timmons Consulting,Inc。
http://www.crtimmonsinc.com/


2003年9月23日22:26:59 -0700, pe ************ @ hotmail.com (pj)写道:
On 23 Sep 2003 22:26:59 -0700, pe************@hotmail.com (pj) wrote:
(原来,可能是错误的,发布到vc子组。)
(这似乎不是ac#问题,但是Visual Studio c#编译器中存在错误问题,但是,欢迎任何帮助。 ..)


这个小组涵盖编译器问题以及语言问题,所以你的

帖子适合。

做什么其他人什么时候打他们的编译器错误?也许你们其他人都知道如何解码这些信息
找出哪些文件和行号混淆了编译器?
(Was originally, probably wrongly, posted to the vc subgroup.)
(This doesn''t appear to be a c# problem, but a problem with a bug in
the Visual Studio c# compiler, but, any help will be welcome...)
This group covers compiler issues as well as language issues so your
post fits right in.
What do other people do when they hit
compiler bugs ? Perhaps you others know how to decode this information
to find out what file and line number is confusing the compiler ?




不知道,它不是我的工作。当编译器生成一个

内部错误时(我想我实际上在1.0框架中有一个错误)

我查看错误消息并尝试改变一切直到

代码编译。此外,你应该让编译器制造商(即微软的b
)知道他们是否真的不知道这个bug。这就是全部。

-
http:// www.kynosarges.de


Christoph Nahr< ch ************ @ kynosarges.de>在消息新闻中写道:< hl ******************************** @ 4ax.com>。 ..
Christoph Nahr <ch************@kynosarges.de> wrote in message news:<hl********************************@4ax.com>. ..
2003年9月23日22:26:59 -0700, pe * ***********@hotmail.com (pj)写道:
On 23 Sep 2003 22:26:59 -0700, pe************@hotmail.com (pj) wrote:
(最初,可能是错误的,发布到vc子组。)
(这似乎不是ac#问题,但是Visual Studio c#编译器中存在错误问题,但是,欢迎任何帮助......)
(Was originally, probably wrongly, posted to the vc subgroup.)
(This doesn''t appear to be a c# problem, but a problem with a bug in
the Visual Studio c# compiler, but, any help will be welcome...)

<这个小组涵盖了编译器问题以及语言问题,所以你的
帖子适合。



This group covers compiler issues as well as language issues so your
post fits right in.

其他人在点击时会做什么?br />
编译器错误?也许你们其他人都知道如何解码这些信息
找出哪些文件和行号混淆了编译器?
What do other people do when they hit
compiler bugs ? Perhaps you others know how to decode this information
to find out what file and line number is confusing the compiler ?



不知道,它不是我的工作。当编译器生成一个
内部错误时(我想我实际上在1.0框架中有一个,一次)
我查看错误消息并尝试改变一切,直到
代码编译。此外,你应该让编译器制造商(即微软)知道他们是否不知道这个bug。这就是全部。



Don''t know, and it''s not my job. When a compiler generates an
internal error (I think I actually got one in the 1.0 framework, once)
I look at the error message and try to change things around until the
code compiles. Moreover, you should let the compiler makers (i.e.
Microsoft) know if they aren''t alreay aware of the bug. That''s all.



我想你在这里切入了问题的核心。调试C#编译器也不是我的工作,而且如果编译器编写者不能

打扰告诉我在什么文件和行中问题是,我不太倾向于努力调试它。如果他们至少告诉我

问题是什么文件,我可能更倾向于尝试;但是,正如我理解它,他们告诉我,你的代码中有一些东西我们无法处理; b $ b无法处理;改变你的代码。我不愿随意开始

置换代码的随机部分(因为担心这将是一个巨大的

时间沉没的低回报),所以这对我来说最简单回滚到前一天版本的
,并重新设计并重写最近的代码。

课程,然后我完全避免诊断错误。


I guess here you cut to the heart of the problem. It also isn''t my job
to debug the C# compiler, and if the compiler writers couldn''t be
bothered to tell me in what file and line the problem is, I''m less
inclined to work hard at debugging it. If they told me at least in
what file the problem was, I might be more inclined to try; but, as I
understand it, they''re telling me, "there is something in your code we
can''t handle; change your code". I am reluctant to start randomly
permuting random parts of the code (for fear that that will be a huge
time sink of low reward), so it is easiest for me to rollback to a
previous day''s version, and redesign and rewrite recent code. Of
course, then I avoid diagnosing the bug entirely.


这篇关于内部错误 - 如何处理错误(?)MSC#编译器?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆