By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,694 Members | 1,332 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,694 IT Pros & Developers. It's quick & easy.

Unhandled exception

P: n/a
Hi there,

Im experiencing an unhandled exception that seems to be impossible for
me to catch. I am launching an assembly of mine from within another
assembly using the Process object. Once the process finishes it causes an
unhandled exception, even though both host and child process have all thread
exceptions handled.

Unfortunately this is making debugging a complete and utter nightmare as
the application has already terminated by the time the standard unhandled
excaption dialog appears with this info in...

EventType : clr20r3 P1 : <child assembly> P2 : 1.3.2323.22525
P3 : 44648dad
P4 : mscorlib P5 : 2.0.0.0 P6 : 4333ab80 P7 : 11d0 P8 : 27
P9 : system.applicationexception

Any ideas what this is supposed to mean exactly? It has no relevance to
me but if I could just know what the exception is exactly then this could
help, "applicationexception" doesn't help me in the slightest as i have 3
assemblies that derive from said applicationexception that are being used
during this process.

I can only presume that this error could be down to the disposing of an
object by the garbage collector, I cant think of any other reason why code
would remain to be processed after the last line of code has been passed..

Thanks loads in advance if anyone can help me with this.

Nick.
May 12 '06 #1
Share this Question
Share on Google+
3 Replies


P: n/a
Hi there,

Just to add, I've managed to get rid of the exception by disposing a
specific object before the application exits. The object was only disposing
a mutex so I'm not quite sure how this would cause an exception at garbage
collection time.. Anyway, it's gone now so I guess I shouldn't complain!

Nick.

"NickP" <a@a.com> wrote in message
news:uG**************@TK2MSFTNGP04.phx.gbl...
Hi there,

Im experiencing an unhandled exception that seems to be impossible for
me to catch. I am launching an assembly of mine from within another
assembly using the Process object. Once the process finishes it causes an
unhandled exception, even though both host and child process have all
thread exceptions handled.

Unfortunately this is making debugging a complete and utter nightmare
as the application has already terminated by the time the standard
unhandled excaption dialog appears with this info in...

EventType : clr20r3 P1 : <child assembly> P2 : 1.3.2323.22525
P3 : 44648dad
P4 : mscorlib P5 : 2.0.0.0 P6 : 4333ab80 P7 : 11d0 P8 : 27
P9 : system.applicationexception

Any ideas what this is supposed to mean exactly? It has no relevance
to me but if I could just know what the exception is exactly then this
could help, "applicationexception" doesn't help me in the slightest as i
have 3 assemblies that derive from said applicationexception that are
being used during this process.

I can only presume that this error could be down to the disposing of an
object by the garbage collector, I cant think of any other reason why code
would remain to be processed after the last line of code has been passed..

Thanks loads in advance if anyone can help me with this.

Nick.

May 12 '06 #2

P: n/a
Nick,
You could use the AppDomain object to register a handler for Unhandled
Exceptions in your app, allowing you to see more detail about the
problem you're occuring.
Module Module1

Sub Main()

AddHandler AppDomain.CurrentDomain.UnhandledException,
AddressOf Unhandled

Throw New Exception("Unhandled Exception")

End Sub

Private Sub Unhandled(ByVal sender As Object, ByVal e As
UnhandledExceptionEventArgs)

Console.WriteLine("Unhandled Exception of Type " &
e.ExceptionObject.GetType.ToString)
Console.WriteLine(e.ExceptionObject.ToString)
Console.ReadLine()

End Sub

End Module
john

May 12 '06 #3

P: n/a
Hi John,

Indeed I have been, and also the thread exception. But neither would
catch this exception, I believe it was because the application had already
terminated and it was occuring during garbage collection. All sorted now
though thankfully, cheers for your input.

Nick.

"jayeldee" <ja******@gmail.com> wrote in message
news:11**********************@d71g2000cwd.googlegr oups.com...
Nick,
You could use the AppDomain object to register a handler for Unhandled
Exceptions in your app, allowing you to see more detail about the
problem you're occuring.
Module Module1

Sub Main()

AddHandler AppDomain.CurrentDomain.UnhandledException,
AddressOf Unhandled

Throw New Exception("Unhandled Exception")

End Sub

Private Sub Unhandled(ByVal sender As Object, ByVal e As
UnhandledExceptionEventArgs)

Console.WriteLine("Unhandled Exception of Type " &
e.ExceptionObject.GetType.ToString)
Console.WriteLine(e.ExceptionObject.ToString)
Console.ReadLine()

End Sub

End Module
john

May 15 '06 #4

This discussion thread is closed

Replies have been disabled for this discussion.