On Sat, Jan 17, 2009 at 3:42 PM, Dino Viehland wrote:
> I think it is because new StackTrace(exception) requires or required trust at
> one point in time (same reason for the catch of MemberAccessException).
>
> Looking at mscorlib now it would seem that StackTrace(e) is now
> SecuritySafeCritic
Silverlight as well.
> -Original Message-
> From: users-boun...@lists.ironpython.com [mailto:users-
> boun...@lists.ironpython.com] On Behalf Of Dan Eloff
> Sent: Saturday, January 17, 2009 12:27 PM
> To: Discussion of IronPython
> Subject: Re: [IronPython] Odd tracebacks
>
I look forward to seeing what you find :)
-Original Message-
From: users-boun...@lists.ironpython.com
[mailto:users-boun...@lists.ironpython.com] On Behalf Of Dan Eloff
Sent: Friday, January 16, 2009 11:18 AM
To: Discussion of IronPython
Subject: Re: [IronPython] Odd tracebacks
This e
hon.com] On Behalf Of Dan Eloff
> Sent: Friday, January 16, 2009 11:18 AM
> To: Discussion of IronPython
> Subject: Re: [IronPython] Odd tracebacks
>
> This extraneous stack trace seems to happen on every exception. I've
> confirmed that it's an IronPython problem, not silverlig
IronPython
Subject: Re: [IronPython] Odd tracebacks
This extraneous stack trace seems to happen on every exception. I've
confirmed that it's an IronPython problem, not silverlight. It only
ever consists of these two, and the debugger confirms that they aren't
called on the error path.
This extraneous stack trace seems to happen on every exception. I've
confirmed that it's an IronPython problem, not silverlight. It only
ever consists of these two, and the debugger confirms that they aren't
called on the error path.
at pairwise in game/utils\functions.py, line 46
at __getattr__ i
On Fri, Jan 2, 2009 at 12:33 PM, Dino Viehland wrote:
> Are there other exceptions being thrown, potentially somewhere on the stack
> below game\models\__init__.py on line 144? Maybe we're calling a built-in
> function somewhere that's calling back into your code and is doing something
> funky
IronPython
Subject: [IronPython] Odd tracebacks
I've been experiencing off tracebacks for several weeks now, mostly I
just ignore them because it could be my fault, and it's not a blocker.
On AttributeErrors I see very strange tracebacks, impossible
tracebacks, sometimes even misleading
I've been experiencing off tracebacks for several weeks now, mostly I
just ignore them because it could be my fault, and it's not a blocker.
On AttributeErrors I see very strange tracebacks, impossible
tracebacks, sometimes even misleading tracebacks.
Have a look at this (complete) traceback:
--
