Hi Martin, Ah thanks, that sorts it. I thought it might be the case... I was tearing my hair out initially when I received a message regarding a thread needing to be STA...
I learnt more than I wanted to with that regard. I will file that in the good to know box. And, thanks for your explanation, makes sense; but I'm still left with that hollow feeling... on account of the Avalon big black window bug http://lab.msdn.microsoft.com/productfeedback/viewfeedback.aspx?feedbackid=2e26e6c9-b7b1-4a5d-b661-d834330deb73 :-) Good to know it's that it's consistent across XAML, IronPython and C#. Thanks, Liam On 12/14/05, Martin Maly <[EMAIL PROTECTED]> wrote: > Hi Liam, > > The root of the problem is that you create separate thread. Once you do that, > the second thread doesn't have global try: except: statement in it so all > exceptions fly right through to the OS, which kills the process and displays > Dr. Watson. > > You can do something like: > > def start(): > try: > app = MyApp() > app.Run() > except Exception, e: > print e > > t = Thread(start) > t.ApartmentState = ApartmentState.STA > t.Start() > t.Join() > > to catch the 2nd thread's exceptions and get diagnostics. > > > I hope this helps > Martin > > > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Liam Clarke > Sent: Tuesday, December 13, 2005 10:45 PM > To: Discussion of IronPython > Subject: Re: [IronPython] DW.exe... > > Hi Martin, > > It's IronPython 0.9.6 on .NET 2.0.50727.42; and I'm running the > console, I guess, if that includes ironpythonconsole.exe > <script_name>. The script I'm trying to work with is here - > http://rafb.net/paste/results/mk0Jrn95.html (for the next 24 hours at least) > > Regards, > > Liam Clarke > > On 12/14/05, Martin Maly <[EMAIL PROTECTED]> wrote: > > Are you using IronPython 0.9.6? The 0.9.6 version of IronPython should > > catch unhandled exceptions and print stack trace rather than passing the > > exception to the OS (for Dr. Watson - hence DW.exe) > > > > As for the 0.9.5 version of IronPytohn, there was a known problem, a change > > in our exception handling logic that would pass unhandled exceptions to the > > OS which then triggers Watson. > > > > Please let me know if you have problems on IronPython 0.9.6 and, if so, do > > you use IronPython from console (IronPythonConsole.exe) or is it embedded > > in another application? > > > > Thanks > > Martin > > > > -----Original Message----- > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Liam Clarke > > Sent: Tuesday, December 13, 2005 9:14 PM > > To: Discussion of IronPython > > Subject: [IronPython] DW.exe... > > > > Hi all, > > > > Playing with the November Avalon CTP, and when my script causes an > > exception through an incorrect parameter or similar (in the Avalon > > bits) a new process of DW.exe gets spawned. > > > > I see that DW is just dumping data for a bug report, but filing a bug > > report for a bad argument is a bit ludicrous, I thought. > > > > Is this IronPython or solely Avalon doing this? > > > > Can anyone offer suggestions on preventing it? > > > > Regards, > > > > Liam Clarke > > _______________________________________________ > > users mailing list > > [email protected] > > http://lists.ironpython.com/listinfo.cgi/users-ironpython.com > > _______________________________________________ > > users mailing list > > [email protected] > > http://lists.ironpython.com/listinfo.cgi/users-ironpython.com > > > _______________________________________________ > users mailing list > [email protected] > http://lists.ironpython.com/listinfo.cgi/users-ironpython.com > _______________________________________________ > users mailing list > [email protected] > http://lists.ironpython.com/listinfo.cgi/users-ironpython.com > _______________________________________________ users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
