Include stack trace to error message when constructing a new Error with another Error as argument.

Include stack trace to error message when constructing a new Error with another Error as argument.


BUG=60240
TEST=cctest/RethrowWrapStackTrace

[Yang, 2012-02-06 16:43:14]

Not sure whether this makes sense, as this is not really part of the spec.
Basically this changes chaining Errors when rethrown from this

try {
  error;
} catch (e) {  
  throw new Error(e.stack);
}

to
try {
  error;
} catch (e) {  
  throw new Error(e);
}

Also see the thread here:
http://code.google.com/p/chromium/issues/detail?id=60240

[Yang, 2012-02-06 16:46:16]

On 2012/02/06 16:43:14, Yang wrote:
> Not sure whether this makes sense, as this is not really part of the spec.
> Basically this changes chaining Errors when rethrown from this
> 
> try {
>   error;
> } catch (e) {  
>   throw new Error(e.stack);
> }
> 
> to
> try {
>   error;
> } catch (e) {  
>   throw new Error(e);
> }
> 
> Also see the thread here:
> http://code.google.com/p/chromium/issues/detail?id=60240

Also note that this CL depends on http://codereview.chromium.org/9310122/

[Yang, 2012-02-07 07:12:36]

On 2012/02/06 16:46:16, Yang wrote:
> On 2012/02/06 16:43:14, Yang wrote:
> > Not sure whether this makes sense, as this is not really part of the spec.
> > Basically this changes chaining Errors when rethrown from this
> > 
> > try {
> >   error;
> > } catch (e) {  
> >   throw new Error(e.stack);
> > }
> > 
> > to
> > try {
> >   error;
> > } catch (e) {  
> >   throw new Error(e);
> > }
> > 
> > Also see the thread here:
> > http://code.google.com/p/chromium/issues/detail?id=60240
> 
> Also note that this CL depends on http://codereview.chromium.org/9310122/

On another thought, don't review this. There is no point introducing behavior
that no other browser has, even if it makes sense.