DrKoch (2/22/2007)

---

It is very cool to see the line numbers of *my* source code if it throws an exception - <- happy!

Would be even better if you could find a way to distinguish between exceptions form "my" code and exceptions from somewhere else in RE.

It is nice that there opens a "send report" box for the latter, but this is surely the wrong thing for my typos.

What about highlighting the stupid line in the editor, to push my nose towards that typo...

Hrm, functionality to show the line numbers in your code should be there, but will add a bug to that this can be checked and re-implemented if it was broken somewhere along the way.  Bug 796

It's going to be really hard for us to tell, when running a system, whether the exception was in your code or ours.  I think we'd end up resorting to having to parse the stack trace.  Also, a lot of the times the exception will actually be in our code, but the error could be in yours   NullReferenceExceptions come to mind, when we are given a null and expecting and object.  We'll throw the exception, but the outside code was the problem.

We might consider removing that send from system exceptions altogether if it gets to be a problem to manage on our end.

Highlighting would be nice, but that would force us to parse stack trace text and that is difficult and error prone, so we don't have any near term plans to tackle that one, unfortunately.

Good, I'll close that bug.  At one time it was not there and we specifically made changes to accomidate it, so I thought we'd broken this somewhere along the journey.