| 
 | 
 | 
 Chromium Code Reviews
 Chromium Code Reviews Issue 
            2110683007:
    Use toString tag to format receiver in stack traces  (Closed)
    
  
    Issue 
            2110683007:
    Use toString tag to format receiver in stack traces  (Closed) 
  | DescriptionUse toString tag to format receiver in stack traces
This concerns formatting of calls to, e.g., Math.acos in stack traces,
in which the receiver is an object with an attached toString tag. If
such a tag exists, use it to format the receiver typename to ensure that
the stack trace includes 'Math.acos' instead of 'Object.acos'.
R=yangguo@chromium.org
BUG=
Committed: https://crrev.com/971468031a911cd6d90524af2fce64833aeafc40
Cr-Commit-Position: refs/heads/master@{#37513}
   Patch Set 1 #Patch Set 2 : Updated dependencies #
      Total comments: 2
      
     Patch Set 3 : Undefined/null CHECK in GetConstructorName #Patch Set 4 : Rebase on master #
 Dependent Patchsets: Messages
    Total messages: 37 (18 generated)
     
 The CQ bit was checked by jgruber@chromium.org to run a CQ dry run 
 Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or... 
 The CQ bit was unchecked by commit-bot@chromium.org 
 Dry run: Try jobs failed on following builders: v8_linux64_avx2_rel_ng on master.tryserver.v8 (JOB_FAILED, http://build.chromium.org/p/tryserver.v8/builders/v8_linux64_avx2_rel_ng/buil...) v8_linux64_avx2_rel_ng_triggered on master.tryserver.v8 (JOB_FAILED, http://build.chromium.org/p/tryserver.v8/builders/v8_linux64_avx2_rel_ng_trig...) 
 The CQ bit was checked by jgruber@chromium.org to run a CQ dry run 
 Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or... 
 The CQ bit was unchecked by commit-bot@chromium.org 
 Dry run: This issue passed the CQ dry run. 
 
 Description was changed from ========== Use toString tag to format receiver in stack traces This concerns formatting of calls to, e.g., Math.acos in stack traces, in which the receiver is an object with an attached toString tag. If such a tag exists, use it to format the receiver typename to ensure that the stack trace includes 'Math.acos' instead of 'Object.acos'. R=yangguo@chromium.org BUG= ========== to ========== Use toString tag to format receiver in stack traces This concerns formatting of calls to, e.g., Math.acos in stack traces, in which the receiver is an object with an attached toString tag. If such a tag exists, use it to format the receiver typename to ensure that the stack trace includes 'Math.acos' instead of 'Object.acos'. R=yangguo@chromium.org BUG= ========== 
 jgruber@chromium.org changed reviewers: + verwaest@chromium.org 
 nice, lgtm 
 LGTM. https://codereview.chromium.org/2110683007/diff/20001/src/runtime/runtime-obj... File src/runtime/runtime-object.cc (right): https://codereview.chromium.org/2110683007/diff/20001/src/runtime/runtime-obj... src/runtime/runtime-object.cc:767: ASSIGN_RETURN_FAILURE_ON_EXCEPTION(isolate, recv, Can this actually throw? If it does, should we catch that and instead return some default string? 
 https://codereview.chromium.org/2110683007/diff/20001/src/runtime/runtime-obj... File src/runtime/runtime-object.cc (right): https://codereview.chromium.org/2110683007/diff/20001/src/runtime/runtime-obj... src/runtime/runtime-object.cc:767: ASSIGN_RETURN_FAILURE_ON_EXCEPTION(isolate, recv, On 2016/07/04 10:55:38, Yang wrote: > Can this actually throw? If it does, should we catch that and instead return > some default string? Apparently, Object::ToObject() throws if null or undefined are passed. We ensure this is not the case in messages.js:GetTypeName(). Added a CHECK here and removed the ASSIGN_RETURN_FAILURE_ON_EXCEPTION use. 
 The CQ bit was checked by jgruber@chromium.org to run a CQ dry run 
 Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or... 
 The CQ bit was unchecked by commit-bot@chromium.org 
 Dry run: Try jobs failed on following builders: v8_linux_dbg_ng on master.tryserver.v8 (JOB_FAILED, http://build.chromium.org/p/tryserver.v8/builders/v8_linux_dbg_ng/builds/8448) v8_linux_mipsel_compile_rel on master.tryserver.v8 (JOB_FAILED, http://build.chromium.org/p/tryserver.v8/builders/v8_linux_mipsel_compile_rel...) v8_linux_nodcheck_rel_ng on master.tryserver.v8 (JOB_FAILED, http://build.chromium.org/p/tryserver.v8/builders/v8_linux_nodcheck_rel_ng/bu...) 
 The CQ bit was checked by jgruber@chromium.org to run a CQ dry run 
 Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or... 
 The CQ bit was unchecked by commit-bot@chromium.org 
 Dry run: Try jobs failed on following builders: v8_mac_rel_ng on master.tryserver.v8 (JOB_FAILED, http://build.chromium.org/p/tryserver.v8/builders/v8_mac_rel_ng/builds/4400) 
 The CQ bit was checked by jgruber@chromium.org 
 The patchset sent to the CQ was uploaded after l-g-t-m from yangguo@chromium.org, verwaest@chromium.org Link to the patchset: https://codereview.chromium.org/2110683007/#ps60001 (title: "Rebase on master") 
 CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or... 
 The CQ bit was unchecked by commit-bot@chromium.org 
 Try jobs failed on following builders: v8_mac_rel_ng on master.tryserver.v8 (JOB_FAILED, http://build.chromium.org/p/tryserver.v8/builders/v8_mac_rel_ng/builds/4407) 
 The CQ bit was checked by machenbach@chromium.org to run a CQ dry run 
 Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or... 
 The CQ bit was unchecked by commit-bot@chromium.org 
 Dry run: This issue passed the CQ dry run. 
 The CQ bit was checked by jgruber@chromium.org 
 CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or... 
 
            
              
                Message was sent while issue was closed.
              
            
             Description was changed from ========== Use toString tag to format receiver in stack traces This concerns formatting of calls to, e.g., Math.acos in stack traces, in which the receiver is an object with an attached toString tag. If such a tag exists, use it to format the receiver typename to ensure that the stack trace includes 'Math.acos' instead of 'Object.acos'. R=yangguo@chromium.org BUG= ========== to ========== Use toString tag to format receiver in stack traces This concerns formatting of calls to, e.g., Math.acos in stack traces, in which the receiver is an object with an attached toString tag. If such a tag exists, use it to format the receiver typename to ensure that the stack trace includes 'Math.acos' instead of 'Object.acos'. R=yangguo@chromium.org BUG= ========== 
 
            
              
                Message was sent while issue was closed.
              
            
             Committed patchset #4 (id:60001) 
 
            
              
                Message was sent while issue was closed.
              
            
             Description was changed from ========== Use toString tag to format receiver in stack traces This concerns formatting of calls to, e.g., Math.acos in stack traces, in which the receiver is an object with an attached toString tag. If such a tag exists, use it to format the receiver typename to ensure that the stack trace includes 'Math.acos' instead of 'Object.acos'. R=yangguo@chromium.org BUG= ========== to ========== Use toString tag to format receiver in stack traces This concerns formatting of calls to, e.g., Math.acos in stack traces, in which the receiver is an object with an attached toString tag. If such a tag exists, use it to format the receiver typename to ensure that the stack trace includes 'Math.acos' instead of 'Object.acos'. R=yangguo@chromium.org BUG= Committed: https://crrev.com/971468031a911cd6d90524af2fce64833aeafc40 Cr-Commit-Position: refs/heads/master@{#37513} ========== 
 
            
              
                Message was sent while issue was closed.
              
            
             Patchset 4 (id:??) landed as https://crrev.com/971468031a911cd6d90524af2fce64833aeafc40 Cr-Commit-Position: refs/heads/master@{#37513} | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
