![]() |
![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() |
| Welcome to Windows Vista Forums. Our forum is dedicated to helping you find solutions with any problems, errors or issues you are experiencing with Windows Vista. The Vista forum also covers news and updates and has an extensive Windows Vista tutorial section that covers a wide range of tips and tricks. |
| |||||||
![]() |
| |
| | #1 (permalink) |
| | Suggestion: Add function arguments to stack trace 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 |
My System Specs![]() |
| | #2 (permalink) |
| | Re: Suggestion: Add function arguments to stack trace 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 "Axel Dahmen" <keentoknow@xxxxxx> wrote in message news:uZjyR1K1JHA.4272@xxxxxx 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 |
My System Specs![]() |
| | #3 (permalink) |
| | Re: Suggestion: Add function arguments to stack trace OK, I see. I've added a suggestion there then. Axel ------------------- "Cor Ligthert[MVP]" <Notmyfirstname@xxxxxx> schrieb im Newsbeitrag news:efuQNFS1JHA.1900@xxxxxx Quote: > 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 > > "Axel Dahmen" <keentoknow@xxxxxx> wrote in message > news:uZjyR1K1JHA.4272@xxxxxx > 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 > |
My System Specs![]() |
![]() |
| Thread Tools | |
| |
Similar Threads | ||||
| Thread | Forum | |||
| C++ -- GUI Hang Stack Trace -- Help Needed | .NET General | |||
| Getting arguments from STDIN when command line arguments are missing | PowerShell | |||
| Passing arguments to a function | PowerShell | |||
| Suggestion: Consider shorter standard names for Alias.Function, and Variable PSDrives | PowerShell | |||