836916 - Stack trace in caught error (error.stack) no longer has arguments

Status: RESOLVED WONTFIX

(Core :: JavaScript Engine, defect)

Description

[javascriptjedi]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20100101 Firefox/17.0
Build ID: 20130107124423

Steps to reproduce:

Generate an error object via try { ... some code with an exception ... } catch (e) {};


Actual results:

e.stack contains a stack trace without any arguments.


Expected results:

In versions of Firefox before FF14, arguments were present. for FF version >= 14, no arguments are present.

There's no valid reason to hide the arguments for security purposes, as they can be discovered via stack walking.

If this was done intentionally for some purpose, please explain.

Comment 1

[(mostly gone) XtC4UaLL [:xtc4uall]]

Care to attach a reduced Testcase showing the Issue?

Comment 2

[[:Aleksej]]

(a guess)

Comment 3

[Boris Zbarsky [:bzbarsky]]

Yep.  Reporter, see bug 744842 comment 0 for the reason the behavior changed.

Comment 4

[Nickolay_Ponomarev]

Since this was a deliberate change (per bug 744842 comment 0), I'm assuming the request to undo it should be wontfix.

Comment 5

[txema.gonz]

(In reply to Nickolay_Ponomarev from comment #4)
> Since this was a deliberate change (per bug 744842 comment 0), I'm assuming
> the request to undo it should be wontfix.

Till version 14, I was using a framework https://github.com/txemagon/lluvia-Project that allowed dynamic methods by defining "function method_missing". If no arguments are provided in the error stack, this feature is over. If this is not a bug, how do I overcome this backward uncompatibility? Does anyone know?

Thank you.

Comment 6

[Nickolay_Ponomarev]

(In reply to txema.gonz from comment #5)
> Till version 14, I was using a framework
> https://github.com/txemagon/lluvia-Project that allowed dynamic methods by
> defining "function method_missing".
I think JS proxies can help here: http://wiki.ecmascript.org/doku.php?id=harmony:direct_proxies