On 7/28/05, Rodrigo B. de Oliveira <[EMAIL PROTECTED]> wrote: > On 7/28/05, Rodrigo B. de Oliveira <[EMAIL PROTECTED]> wrote: > > ... > > I'm getting off-by-one errors only with raise/throw statements: > > > > The behavior is actually a little more complex but still predictable. > The stack trace entry for the raise line is always the line of the > next statement in the same method: >
The workaround was to emit debugging information again for a Nop just after the raise statement. Now the lines are reported correctly in both runtimes. -- bamboo http://blogs.codehaus.org/people/bamboo/ Got objects? http://www.db4o.com/ _______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
