[Mono-list] Tracing thrown exceptions on application start
Aleksandar Dezelin
Aleksandar Dezelin <dezelin@gmail.com>
Mon, 21 Feb 2005 16:57:29 +0100
On Mon, 21 Feb 2005 16:45:06 +0100, Paolo Molaro <lupus@ximian.com> wrote:
> On 02/21/05 Aleksandar Dezelin wrote:
> > I have a small test application. I run it with the following command:
> > mono --debug --trace=T:System.Exception Test.exe
> >
> > This is what I get displayed in console window:
> >
> > [skynet@dezelin32 lib]$ mono --debug --trace=T:System.Exception
> > Server.exe --breakonex
> > ENTER: System.Exception:.ctor
> > (string)(this:0x96b7f88[System.OutOfMemoryException Server.exe],
> > [STRING:0x96b8fc0:Out of memory], )
> > LEAVE: System.Exception:.ctor (string)
> [...]
> You can ignore the first few traces: as you can see we just create some
> exception objects, these are not thrown.
>
Ok. Those exceptions must exist in case there's no memory left for the
runtime to create them at the time they're thrown.
> > ENTER: System.Exception:.ctor
> > (string)(this:0x9685e00[System.Xml.XmlException Server.exe],
> > [STRING:0x96c1e60:invalid encoding specification.], )
>
> Your real issue is this, most likely, or the next:
>
> > ENTER: System.Exception:.ctor
> > (string)(this:0x9855ea8[System.IndexOutOfRangeException Server.exe],
> > [STRING:0x985aa00:Array index is out of range.], )
>
> An out of range exception.
>
> > How can I see where are those exceptions thrown?
> > Project is compiled with debugging info on.
>
> See the stack trace of the exception that is thrown.
> You can avoid providing an argument to --trace and have the complete
> dump of where the exception was thrown.
>
> lupus
Many thanks.
Cheers
>
> --
> -----------------------------------------------------------------
> lupus@debian.org debian/rules
> lupus@ximian.com Monkeys do it better
> _______________________________________________
> Mono-list maillist - Mono-list@lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-list
>
--
Linux is like wighwam, no windows no gates and apache inside...