Application Quitting with no Error

  • Thread starter Thread starter Robert Bouillon
  • Start date Start date
R

Robert Bouillon

I'm using Aspects for my middle-tier data access, and on call interception
the application quits without error. It's inconsistent and I've found no
solid repro.

I'm assuming the CLR is encountering an error it can't handle, but I can't
reproduce it consistently so it's hard to determine how this is happening
exactly. The object is constructed, and then on property access the
application quits.

The aspect is used in other places (And is executed well over 50 times)
before it crashes. It only crashes in one specific class that doesn't do
anything special.

Any ideas? Does the CLR have a log file I can access?

Thanks in Advance.

--ROBERT
 
run the application and set the debugger to break into exceptions.
eventually the exception will cause the program to stop at the offending
line of code if it is user code. otherwise, you will get a break but no
source code will show if it is coming from code that isn't user-written

--
Regards,
Alvin Bruney - ASP.NET MVP

[Shameless Author Plug]
The Microsoft Office Web Components Black Book with .NET
Now available @ www.lulu.com/owc, Amazon.com etc
 
Alvin,

"Break Into" is the current setting for how the debugger in my project
handles CLR exceptions.

I've located the line of code that breaks the application. If I put a
breakpoint on the line of code and press F11 (Step Into), then I get a
message box stating, "There is no source code for this location" (or
something similar). When I press OK the application exits.

Also, oddly enough, if I access another property in the object prior to
accessing my desired property, the application seems to work.


bool test = bc.IsPrimaryKeySet; //Line of Code inserted that
allows my code to function properly
BarcodeType bct = bc.Type; //Application quits here if
above line is not present
if(bct==BarcodeType.UPCE)
bc = bc.ConvertTo(BarcodeType.UPCA);


On a side note, I've had problems in the past with Aspects, as the objects
are treated as remoted objects because they are accessed across contexts. If
the code breaks from within the remoted object, Visual Studio will not break
inside of the exception unless a breakpoint has already been set in the
remoted object's context. This does not seem to be the case here, however,
because I'm getting no indication of an exception thrown and my aspect is
not being fully executed as it normally would under the condition of an
exception.

Thanks for your reply. Any additional ideas?

--ROBERT


Alvin Bruney said:
run the application and set the debugger to break into exceptions.
eventually the exception will cause the program to stop at the offending
line of code if it is user code. otherwise, you will get a break but no
source code will show if it is coming from code that isn't user-written

--
Regards,
Alvin Bruney - ASP.NET MVP

[Shameless Author Plug]
The Microsoft Office Web Components Black Book with .NET
Now available @ www.lulu.com/owc, Amazon.com etc
Robert Bouillon said:
I'm using Aspects for my middle-tier data access, and on call interception
the application quits without error. It's inconsistent and I've found no
solid repro.

I'm assuming the CLR is encountering an error it can't handle, but I can't
reproduce it consistently so it's hard to determine how this is happening
exactly. The object is constructed, and then on property access the
application quits.

The aspect is used in other places (And is executed well over 50 times)
before it crashes. It only crashes in one specific class that doesn't do
anything special.

Any ideas? Does the CLR have a log file I can access?

Thanks in Advance.

--ROBERT
Click to expand...
Click to expand...
 
Back
Top