On Fri, 2006-05-12 at 17:07 -0400, Miguel de Icaza wrote:
Hello,

> What is the best way to pursue troubleshooting this. We have tried
> different approaches such as using mono --trace and
> Console.WriteLines, but have made no significant steps forward.

Send a SIGQUIT signal to the Mono process, which will dump the stack
traces of all threads.

You need a modern Mono (at least 1.1.14) for this feature to work.

Thanks, for the information. I saw that Friday morning when I was looking at the release notes before upgrading to Mono 1.1.15. After upgrading to 1.1.15, the application has run all weekend. Something fixed my problem between 1.1.13.4 and 1.1.15.
*************************************************************************
The information contained in this communication is confidential, is
intended only for the use of the recipient named above, and may be
legally privileged.

If the reader of this message is not the intended recipient, you are 
hereby notified that any dissemination, distribution or copying of this
communication is strictly prohibited.

If you have received this communication in error, please resend this
communication to the sender and delete the original message or any copy
of it from your computer system.

Thank you.
*************************************************************************
_______________________________________________
Mono-list maillist  -  [email protected]
http://lists.ximian.com/mailman/listinfo/mono-list

Reply via email to