Stack Trace Explorer is always blank

My stack trace explorer is always blank. By "blank" I mean VS.NET shows a
Window with the appropriate title but no text area in which to paste a stack
trace. Does VS.NET have to be in a particular state, like paused for a break
point? Does the stack trace have to come from a particular source?


9 comments
Comment actions Permalink

Use "Explore Stacktrace" command (CtrlShiftE).

Valentin Kipiatkov
CTO and Chief Scientist
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

My stack trace explorer is always blank. By "blank" I mean VS.NET
shows a Window with the appropriate title but no text area in which to
paste a stack trace. Does VS.NET have to be in a particular state,
like paused for a break point? Does the stack trace have to come from
a particular source?



0
Comment actions Permalink

Hello flipdoubt,

This is used when you have an exception while debugging.
Cause an exception to occur in your code, then press CtrlShiftE which opens
the 'Explore Stack Trace' dialog. Finally, press 'Explore' button to send
to 'Stack Trace Explorer'.


My stack trace explorer is always blank. By "blank" I mean VS.NET
shows a Window with the appropriate title but no text area in which to
paste a stack trace. Does VS.NET have to be in a particular state,
like paused for a break point? Does the stack trace have to come from
a particular source?



0
Comment actions Permalink

So you're saying it doesn't work if I catch the exception, right?


0
Comment actions Permalink

Hello flipdoubt,

exactamundo.

So you're saying it doesn't work if I catch the exception, right?



0
Comment actions Permalink

Hello flipdoubt,

The name of this window is confusing, if you want to see the Call Stack press
CtrlAltC.
Incidently, if you do use the Stack Trace Explorer, you first must copy the
exception detail to the clipboard from the link provided in the VS exception
popup because whatever is in the clipboard is what is copied to this window.
The only thing it does is provide links to the sections of code that are
involved with the exception.

So you're saying it doesn't work if I catch the exception, right?



0
Comment actions Permalink

Hello Matthew,

If you are in debugging session, you don't need to use Stack Trace Explorer,
you can navigate directly from Debug Call Stack window. The main purpose
of Stack Trace Explorer is to allow navigation to call stack entries when
you get exception our of debugging session. For example, exception occured
at your customer's site (and you have some code that will allow customer
to copy and send stack trace to you). Then you can copy and paste stack trace
to explorer's window and investigate what has happened.

Sincerely,
Ilya Ryzhenkov

JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


MM> Hello flipdoubt,
MM>
MM> The name of this window is confusing, if you want to see the Call
MM> Stack press
MM> CtrlAltC.
MM> Incidently, if you do use the Stack Trace Explorer, you first must
MM> copy the
MM> exception detail to the clipboard from the link provided in the VS
MM> exception
MM> popup because whatever is in the clipboard is what is copied to this
MM> window.
MM> The only thing it does is provide links to the sections of code that
MM> are
MM> involved with the exception.
>> So you're saying it doesn't work if I catch the exception, right?
>>


0
Comment actions Permalink

... For
example, exception occured at your customer's site (and you have some
code that will allow customer to copy and send stack trace to you).
Then you can copy and paste stack trace to explorer's window and
investigate what has happened.


If we're talking about pasting a stack trace sent by a customer, it does not have to be an uncaught exception, just any string containing a stack trace. This gets back to my original question:

Why is my Stack Trace Explorer blank? After seeing the screenshot, where would I paste the stack trace I find in a customer's error log?

Attachment not added (general error): "stacktraceexplorer.jpg"

0
Comment actions Permalink

I find this confusing too, but you got the wrong window up. You should bring
up the Explore Stack Trace window (not Stack Trace Explorer which you got up
in your screenshot) and paste the exception there. When you click the
Explore button, the Stack Trace Explorer is opened for you.

I think it would be much more intuitive if these two windows were combined
into one window, or at least give an option to paste exceptions directly
into the Stack Trace Explorer.


0
Comment actions Permalink

+10

"Dag Christensen" <anonymous@noreply.com> wrote in message
news:ek1l8b$ued$1@is.intellij.net...
>I find this confusing too, but you got the wrong window up. You should
>bring up the Explore Stack Trace window (not Stack Trace Explorer which you
>got up in your screenshot) and paste the exception there. When you click
>the Explore button, the Stack Trace Explorer is opened for you.
>

I think it would be much more intuitive if these two windows were combined
into one window, or at least give an option to paste exceptions directly
into the Stack Trace Explorer.



0

Please sign in to leave a comment.