|
|
Created:
4 years, 5 months ago by Michael Lippautz Modified:
4 years, 5 months ago CC:
v8-reviews_googlegroups.com Base URL:
https://chromium.googlesource.com/v8/v8.git@master Target Ref:
refs/pending/heads/master Project:
v8 Visibility:
Public. |
DescriptionAdd crash instrumentation for crbug.com/621147
BUG=chromium:621147
LOG=N
R=ishell@chromium.org,cbruni@chromium.org
Committed: https://crrev.com/5ff508a82299f20a0d9828cf73072a4f4772fab8
Cr-Commit-Position: refs/heads/master@{#37328}
Patch Set 1 #Patch Set 2 : Add pc and fp to the strack trace #
Total comments: 2
Patch Set 3 : check value instead of map #
Total comments: 2
Patch Set 4 : Addressed comments #Patch Set 5 : ul -> ull #Messages
Total messages: 32 (13 generated)
Description was changed from ========== Add crash instrumentation for crbug.com/621147 BUG=chromium:621147 LOG=N ========== to ========== Add crash instrumentation for crbug.com/621147 BUG=chromium:621147 LOG=N R=verwaest@chromium.org,cbruni@chromium.org ==========
mlippautz@chromium.org changed reviewers: + cbruni@chromium.org, verwaest@chromium.org
ptal, any further suggestions?
adamk@chromium.org changed reviewers: + adamk@chromium.org
Just a heads-up, if we want this in M52 it needs to land before 5PM Pacific time on Tuesday.
On 2016/06/27 22:43:56, adamk wrote: > Just a heads-up, if we want this in M52 it needs to land before 5PM Pacific time > on Tuesday. To be clear, it needs to be merged into M52 before 5PM PST on Tuesday. Ideally, this should be in tonight's canary so we have more confidence in the change before merging it in. It seems very late for the author and two of the reviewers, and close to EOD in Pacific time as well, but any chance this can be landed before tonight's canary cut (8PM PST)?
On 2016/06/27 23:11:27, sshruthi wrote: > On 2016/06/27 22:43:56, adamk wrote: > > Just a heads-up, if we want this in M52 it needs to land before 5PM Pacific > time > > on Tuesday. > > To be clear, it needs to be merged into M52 before 5PM PST on Tuesday. Ideally, > this should be in tonight's canary so we have more confidence in the change > before merging it in. It seems very late for the author and two of the > reviewers, and close to EOD in Pacific time as well, but any chance this can be > landed before tonight's canary cut (8PM PST)? I don't feel particularly comfortable reviewing this (nor do I have OWNERS in the proper directory), so I don't think landing this today is much safer than waiting for it to be properly reviewed in Munich and landed there.
On 2016/06/27 23:20:52, adamk wrote: > On 2016/06/27 23:11:27, sshruthi wrote: > > On 2016/06/27 22:43:56, adamk wrote: > > > Just a heads-up, if we want this in M52 it needs to land before 5PM Pacific > > time > > > on Tuesday. > > > > To be clear, it needs to be merged into M52 before 5PM PST on Tuesday. > Ideally, > > this should be in tonight's canary so we have more confidence in the change > > before merging it in. It seems very late for the author and two of the > > reviewers, and close to EOD in Pacific time as well, but any chance this can > be > > landed before tonight's canary cut (8PM PST)? > > I don't feel particularly comfortable reviewing this (nor do I have OWNERS in > the proper directory), so I don't think landing this today is much safer than > waiting for it to be properly reviewed in Munich and landed there. Sure, if you don't feel comfortable, then let's definitely wait. Once this lands, please work with govind@ to figure out what's the safest way to get this into the beta build for the week. We should definitely get this into this week's beta build, if it is safe and everything looks good on canary.
ishell@chromium.org changed reviewers: + ishell@chromium.org
https://codereview.chromium.org/2100313002/diff/20001/src/ic/ic.cc File src/ic/ic.cc (right): https://codereview.chromium.org/2100313002/diff/20001/src/ic/ic.cc#newcode2542 src/ic/ic.cc:2542: uintptr_t left_raw = HeapObject::cast(*left)->map_word().ToRawValue(); If left is a broken pointer it will already crash in attempt to load a map. We should compare the lower part of the left value with the hole value.
https://codereview.chromium.org/2100313002/diff/20001/src/ic/ic.cc File src/ic/ic.cc (right): https://codereview.chromium.org/2100313002/diff/20001/src/ic/ic.cc#newcode2542 src/ic/ic.cc:2542: uintptr_t left_raw = HeapObject::cast(*left)->map_word().ToRawValue(); On 2016/06/28 07:07:20, Igor Sheludko wrote: > If left is a broken pointer it will already crash in attempt to load a map. We > should compare the lower part of the left value with the hole value. Oops, thought that it was the map. Reading the values now.
https://codereview.chromium.org/2100313002/diff/40001/src/ic/ic.cc File src/ic/ic.cc (right): https://codereview.chromium.org/2100313002/diff/40001/src/ic/ic.cc#newcode2552 src/ic/ic.cc:2552: isolate()->PushStackTraceAndDie(0xBAAAAAAD, pc(), fp(), 0u); I have a fear that the instructions array could be eliminated in release build since it is not used. I would put the fp() value to the beginning of the instructions buffer and pass the buffer pointer to the PushStackTraceAndDie instead of fp.
https://codereview.chromium.org/2100313002/diff/40001/src/ic/ic.cc File src/ic/ic.cc (right): https://codereview.chromium.org/2100313002/diff/40001/src/ic/ic.cc#newcode2552 src/ic/ic.cc:2552: isolate()->PushStackTraceAndDie(0xBAAAAAAD, pc(), fp(), 0u); On 2016/06/28 09:06:28, Igor Sheludko wrote: > I have a fear that the instructions array could be eliminated in release build > since it is not used. I would put the fp() value to the beginning of the > instructions buffer and pass the buffer pointer to the PushStackTraceAndDie > instead of fp. Done.
lgtm from my side. Maybe Camillo will add comments.
Description was changed from ========== Add crash instrumentation for crbug.com/621147 BUG=chromium:621147 LOG=N R=verwaest@chromium.org,cbruni@chromium.org ========== to ========== Add crash instrumentation for crbug.com/621147 BUG=chromium:621147 LOG=N R=ishell@chromium.org,cbruni@chromium.org ==========
On 2016/06/28 at 09:46:55, ishell wrote: > lgtm from my side. > Maybe Camillo will add comments. Just tried out locally and seems to be fine...
The CQ bit was checked by cbruni@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_win64_rel_ng on master.tryserver.v8 (JOB_FAILED, http://build.chromium.org/p/tryserver.v8/builders/v8_win64_rel_ng/builds/9618)
The CQ bit was checked by mlippautz@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 mlippautz@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from ishell@chromium.org Link to the patchset: https://codereview.chromium.org/2100313002/#ps80001 (title: "ul -> ull")
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 ========== Add crash instrumentation for crbug.com/621147 BUG=chromium:621147 LOG=N R=ishell@chromium.org,cbruni@chromium.org ========== to ========== Add crash instrumentation for crbug.com/621147 BUG=chromium:621147 LOG=N R=ishell@chromium.org,cbruni@chromium.org ==========
Message was sent while issue was closed.
Committed patchset #5 (id:80001)
Message was sent while issue was closed.
Description was changed from ========== Add crash instrumentation for crbug.com/621147 BUG=chromium:621147 LOG=N R=ishell@chromium.org,cbruni@chromium.org ========== to ========== Add crash instrumentation for crbug.com/621147 BUG=chromium:621147 LOG=N R=ishell@chromium.org,cbruni@chromium.org Committed: https://crrev.com/5ff508a82299f20a0d9828cf73072a4f4772fab8 Cr-Commit-Position: refs/heads/master@{#37328} ==========
Message was sent while issue was closed.
Patchset 5 (id:??) landed as https://crrev.com/5ff508a82299f20a0d9828cf73072a4f4772fab8 Cr-Commit-Position: refs/heads/master@{#37328}
Message was sent while issue was closed.
A revert of this CL (patchset #5 id:80001) has been created in https://codereview.chromium.org/2118493002/ by adamk@chromium.org. The reason for reverting is: Instrumentation not needed on master branch. |