Suggestion: Add function arguments to stack trace

A

Axel Dahmen

Hi,

I'm having a problem investigating unexpected exceptions at our production system where these exceptions are logged into a file.

I believe giving a stack trace containing only function prototypes is not sufficient to find a problem. I'd very much prefer a compiler option to add actual argument values to the stack trace.

Something like:

Cannot create a file when that file already exists.

at System.IO.__Error.WinIOError(Int32 errorCode = 123456789, String maybeFullPath = true)
at System.IO.__Error.WinIOError()
at System.IO.File.Move(String sourceFileName = "C:\\Temp\\MyFile.txt", String destFileName = "C:\\Temp\\YourFile.txt")
...

Your thoughts?

Regards,
www.axeldahmen.de
Axel Dahmen
 
C

Cor Ligthert[MVP]

Axel,

First of all this is a discussion newsgroup for developers using Microsoft
programs about direct developing problems, secondly it is used by MSDN to
give help with subscriptions.

However, there is a special website to give suggestions like you do.

http://connect.microsoft.com

Cor

Hi,

I'm having a problem investigating unexpected exceptions at our production
system where these exceptions are logged into a file.

I believe giving a stack trace containing only function prototypes is not
sufficient to find a problem. I'd very much prefer a compiler option to add
actual argument values to the stack trace.

Something like:

Cannot create a file when that file already exists.

at System.IO.__Error.WinIOError(Int32 errorCode = 123456789, String
maybeFullPath = true)
at System.IO.__Error.WinIOError()
at System.IO.File.Move(String sourceFileName = "C:\\Temp\\MyFile.txt",
String destFileName = "C:\\Temp\\YourFile.txt")
...

Your thoughts?

Regards,
www.axeldahmen.de
Axel Dahmen
 
C

Cor Ligthert[MVP]

Axel,

First of all this is a discussion newsgroup for developers using Microsoft
programs about direct developing problems, secondly it is used by MSDN to
give help with subscriptions.

However, there is a special website to give suggestions like you do.

http://connect.microsoft.com

Cor

Hi,

I'm having a problem investigating unexpected exceptions at our production
system where these exceptions are logged into a file.

I believe giving a stack trace containing only function prototypes is not
sufficient to find a problem. I'd very much prefer a compiler option to add
actual argument values to the stack trace.

Something like:

Cannot create a file when that file already exists.

at System.IO.__Error.WinIOError(Int32 errorCode = 123456789, String
maybeFullPath = true)
at System.IO.__Error.WinIOError()
at System.IO.File.Move(String sourceFileName = "C:\\Temp\\MyFile.txt",
String destFileName = "C:\\Temp\\YourFile.txt")
...

Your thoughts?

Regards,
www.axeldahmen.de
Axel Dahmen
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

ASP.NET application generates System.IO.FileNotFoundException 2
File.Move UNC 1
Problem with System.IO.File.Move and Catching Exceptions 1
Howto Identify an Exception? 6
System.IO.IOException: The semaphore timeout period has expired. 2
File.Copy 4
The process cannot access the file 2
Question on unhandled exceptions 4

Top