|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
unhandled exception address of Error?when unhandled error occur on my customer. how i can get the address of
error, like we do on C or Pascal (At 0000:C234)? mtczx***@yahoo.com wrote:
> when unhandled error occur on my customer. how i can get the address of The stack trace includes the method that caused the error. If you ship a> error, > like we do on C or Pascal (At 0000:C234)? pdb file with the executable, you can get line number information too. -- Barry is very interst to see .NET vs Java. in java i see that debug info
stored in the class file itself (isn't it?) after all, now i think that if i not save track after version, the line number not help me. what you think? mtczx***@yahoo.com wrote:
> is very interst to see .NET vs Java. in java i see that debug info Well, the stack trace is in Java too, but it is similar: if you want> stored in > the class file itself (isn't it?) file names and line numbers, then you need to compile with -g (but you can toggle line numbers, etc). > after all, now i think that if i not save track after version, the line I'm sorry, I don't understand this question. Trace after version? With> number > not help me. > > what you think? an old-style error address, you'd need the exact same executable with the exact same source - so the version issues haven't changed. The fact that we now have stack traces through Exception.StackTrace means you have more data than back in the old days of error addresses. -- Barry |
|||||||||||||||||||||||