Loading debug information

  • Thread starter Thread starter Guest
  • Start date Start date
Steve,

You can't. The framework does not ship with debug versions of the
framework DLLs.

What is the stack trace? Are you sure it is not the result of your own
doing?

Can you provide an example which shows the error?
 
Can you tell me how to look at the stack trace? That may help me narrow down
the fault?

Nicholas Paldino said:
Steve,

You can't. The framework does not ship with debug versions of the
framework DLLs.

What is the stack trace? Are you sure it is not the result of your own
doing?

Can you provide an example which shows the error?
 
Steve,

Every exception has a StackTrace property, which exposes an object which
has all the information about the call stack. It should shed more light on
the situation.


--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

Steve Teeples said:
Can you tell me how to look at the stack trace? That may help me narrow
down
the fault?

Nicholas Paldino said:
Steve,

You can't. The framework does not ship with debug versions of the
framework DLLs.

What is the stack trace? Are you sure it is not the result of your
own
doing?

Can you provide an example which shows the error?


--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

Steve Teeples said:
I keep getting the error below.
----------------
An unhandled exception of type 'System.NullReferenceException' occurred
in
Unknown Module.

Additional information: Object reference not set to an instance of an
object.
 
I offer this for any new programmers out there. Not sure if it applies
here but you must instantiate any objects that you create.

so

public HelperClass MyClass;

is not enough, you must also have

myclass=new HelperClass();

otherwise you will get a null object error

HTH for anyone out there

Tal McMahon
 
On the IDE I found the call stack. When in debug mode there is no output to
it, nor does right clicking within the call stack window pull up any menu.
Can you tell me how to activate it? The online help doesn't help.

Nicholas Paldino said:
Steve,

Every exception has a StackTrace property, which exposes an object which
has all the information about the call stack. It should shed more light on
the situation.


--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

Steve Teeples said:
Can you tell me how to look at the stack trace? That may help me narrow
down
the fault?

Nicholas Paldino said:
Steve,

You can't. The framework does not ship with debug versions of the
framework DLLs.

What is the stack trace? Are you sure it is not the result of your
own
doing?

Can you provide an example which shows the error?


--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

I keep getting the error below.
----------------
An unhandled exception of type 'System.NullReferenceException' occurred
in
Unknown Module.

Additional information: Object reference not set to an instance of an
object.
 
I found that the call stack only shows current information when you're at a
break point. The dialog box that appears when the error is generated doesn't
provide any details on where. You mentioned this "StackTrace" property.
When the exception occurs, where do I found this "StackTrace" to view it? Is
it a window within the IDE? The dialog box that appears with the exception
gives no data other than what I mentioned orginally.

Nicholas Paldino said:
Steve,

Every exception has a StackTrace property, which exposes an object which
has all the information about the call stack. It should shed more light on
the situation.


--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

Steve Teeples said:
Can you tell me how to look at the stack trace? That may help me narrow
down
the fault?

Nicholas Paldino said:
Steve,

You can't. The framework does not ship with debug versions of the
framework DLLs.

What is the stack trace? Are you sure it is not the result of your
own
doing?

Can you provide an example which shows the error?


--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

I keep getting the error below.
----------------
An unhandled exception of type 'System.NullReferenceException' occurred
in
Unknown Module.

Additional information: Object reference not set to an instance of an
object.
 
Steve,

If you are in debug mode, and there is no output, then it would be
coming from inside the framework (it would seem exclusively, and not as a
result of something you did).

Can you post a project sample that shows what you are doing which shows
the error?


--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

Steve Teeples said:
On the IDE I found the call stack. When in debug mode there is no output
to
it, nor does right clicking within the call stack window pull up any menu.
Can you tell me how to activate it? The online help doesn't help.

Nicholas Paldino said:
Steve,

Every exception has a StackTrace property, which exposes an object
which
has all the information about the call stack. It should shed more light
on
the situation.


--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

Steve Teeples said:
Can you tell me how to look at the stack trace? That may help me
narrow
down
the fault?

:

Steve,

You can't. The framework does not ship with debug versions of the
framework DLLs.

What is the stack trace? Are you sure it is not the result of
your
own
doing?

Can you provide an example which shows the error?


--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

message
I keep getting the error below.
----------------
An unhandled exception of type 'System.NullReferenceException'
occurred
in
Unknown Module.

Additional information: Object reference not set to an instance of
an
object.
 
Steve,

When an exception is thrown, there is an instance of it you can access
in the catch block of the exception handler. You can access it through the
StackTrace property there.


--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

Steve Teeples said:
I found that the call stack only shows current information when you're at a
break point. The dialog box that appears when the error is generated
doesn't
provide any details on where. You mentioned this "StackTrace" property.
When the exception occurs, where do I found this "StackTrace" to view it?
Is
it a window within the IDE? The dialog box that appears with the
exception
gives no data other than what I mentioned orginally.

Nicholas Paldino said:
Steve,

Every exception has a StackTrace property, which exposes an object
which
has all the information about the call stack. It should shed more light
on
the situation.


--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

Steve Teeples said:
Can you tell me how to look at the stack trace? That may help me
narrow
down
the fault?

:

Steve,

You can't. The framework does not ship with debug versions of the
framework DLLs.

What is the stack trace? Are you sure it is not the result of
your
own
doing?

Can you provide an example which shows the error?


--
- Nicholas Paldino [.NET/C# MVP]
- (e-mail address removed)

message
I keep getting the error below.
----------------
An unhandled exception of type 'System.NullReferenceException'
occurred
in
Unknown Module.

Additional information: Object reference not set to an instance of
an
object.
 
Back
Top