L
Larry Lard
I'm hoping there's a way to do this, because my present technique
wastes a lot of time.
Suppose I have this console app:
Module Module1
Sub Main()
Dim a As Integer = 1
Dim b As Integer = 0
Dim c As Integer = a \ b
End Sub
End Module
When I run this from within the IDE, obviously execution will halt with
a divide by zero exception when attempting to assign to c. The
dialogbox presented to me tells me the exception type, and 'Additional
information' which is in fact the exception's Message property. The
buttons I can click are Break and Continue. If I click Continue,
execution ends, which is fine.
If I click Break, I am now in debug mode in the IDE and can I have the
command line and all the usual debug tools, so I can (in this example)
examine b and see that it is indeed zero, and understand why I got my
exception.
However. In a more real-world example, some of the information that
would help debug would be *in the Exception that has just been thrown*.
My question therefore is:
Once I have clicked Break and entered debug mode, is there any way to
obtain / interrogate / anything! the Exception which got me here?
wastes a lot of time.
Suppose I have this console app:
Module Module1
Sub Main()
Dim a As Integer = 1
Dim b As Integer = 0
Dim c As Integer = a \ b
End Sub
End Module
When I run this from within the IDE, obviously execution will halt with
a divide by zero exception when attempting to assign to c. The
dialogbox presented to me tells me the exception type, and 'Additional
information' which is in fact the exception's Message property. The
buttons I can click are Break and Continue. If I click Continue,
execution ends, which is fine.
If I click Break, I am now in debug mode in the IDE and can I have the
command line and all the usual debug tools, so I can (in this example)
examine b and see that it is indeed zero, and understand why I got my
exception.
However. In a more real-world example, some of the information that
would help debug would be *in the Exception that has just been thrown*.
My question therefore is:
Once I have clicked Break and entered debug mode, is there any way to
obtain / interrogate / anything! the Exception which got me here?