Re: VS crash after debug

Exception Information
code: 0x8013141e
Flags: 0x00000000
Record: 0x000000000000000000
Address; 0x0000000077e55dea



"Trapulo" <trapulo@xxxxxxxxxxxxxxx> wrote in message
news:O4JAV0HXGHA.1084@xxxxxxxxxxxxxxxxxxxxxxx

"Steven Cheng[MSFT]" <stcheng@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:0RckpQSWGHA.5252@xxxxxxxxxxxxxxxxxxxxxxxx
Thanks for your further followup Trapulo,

Well, I think this error message is much more helpful. I've performed
some
further check and did find some "Visual Basic internal compiler error"
related problems. So far I found some similiar issue which occurs in a
VB.NET application(developed in VS 2005) which reference another certain
assembly(class library), and since there is some code in that assembly
doesn't quite define following some certain naming convention that cause
the VB compiler broke. So is this similiar to your case?

I think this is very strange, because compiler compiles my application
without problem. The problem is only after (during) a debug session.

At least you're
referencing an addtional assembly(class library), yes?

Uhm, my DAL layer references MS DAAB 2.0

I think you can
first confirm that it is that particular referenced assembly make the
your
main project's debugging crash, then, try isolating the code in that
class
library to locate the exact code block...

How can I discover what assembly causes compiler's crash? There isn't any
stack report, log, or other useful information when the problem occurs.

I also noticed that when I may terminate VS2005, and then restart it,
reopen the project, and restart a debug, I may "clean" the solution before
I can "debug" it an other time. It takes a lot of time, recompiles all,
start a new instance of asp.net development server (either previuous is
still on and working, and I can continue to use it to debug), and then app
starts without problems).



Thanks




.

Relevant Pages

  • Windows Explorer Application Error
    ... Click on CANCEL to debug the program ... If I click on OK, the error message goes away, I'm back to my desktop, all ... I still cannot use any USB ports or optical drives. ... Windows Memory Diagnostic. ...
    (microsoft.public.windowsxp.perform_maintain)
  • Re: one or more parameter values are not valid
    ... I'm not sure what you mean "dump the call stack". ... What I posted is what I get when I Ctrl+Break, Debug, at the error message. ... Following these steps usually leads to some piece of information that gives us a clue as to how the code is getting entered illegally. ... My Outlook 2003 VBA code has been generating the following error message for at least several of the 25 users running it for the past couple of months. ...
    (microsoft.public.office.developer.outlook.vba)
  • Re: debugging in release mode
    ... I have no doubt that it's a problem of mine and not of the compiler. ... I don't really need optimization ... for the sake of memory space or execution speed. ... shows the differences between the default debug mode and the default release ...
    (microsoft.public.vc.mfc)
  • Re: Whats more important optimisations or debugging?
    ... aiming to make high level debugging as accurate and complete as ... oriented debug chain is appropriate. ... But in either case, barring chip and compiler bugs, the bugs ...
    (comp.arch.embedded)
  • Re: Error a: _mayn.c:12 illegal return type, found int expected void
    ... > a given compiler writer allows or forbids is ... The error message I recieved was in plain english ... >Do you, Jacob, perhaps have a belief that all C programers ... the purpose of lint is to provide error messages. ...
    (comp.compilers.lcc)