|
|
Chromium Code Reviews
DescriptionMove IMMEDIATE_CRASH and OOM_CRASH from wtf to base.
Part of the WTF Headers Audit, and needed for moving PartitionAllocator to base.
BUG=632441
R=danakj@chromium.org, yutak@chromium.org
Patch Set 1 #
Total comments: 2
Patch Set 2 : Remove #define LOGGING_CRASH — unnecessary. #
Total comments: 3
Patch Set 3 : Remove unnecessary #ifndefs. #
Total comments: 2
Patch Set 4 : Restore the necessary comment. #
Total comments: 2
Patch Set 5 : Everything in its right place. #
Messages
Total messages: 38 (17 generated)
The CQ bit was checked by palmer@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...
palmer@chromium.org changed reviewers: + danakj@chromium.org, yutak@chromium.org
Hopefully a quick and easy review for you. Thanks!
The CQ bit was unchecked by commit-bot@chromium.org
Dry run: Try jobs failed on following builders: linux_chromium_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
LGTM but I'd defer the decision to Dana whether this is worthwhile addition in base/.
> LGTM but I'd defer the decision to Dana whether this is > worthwhile addition in base/. The spreadsheet says to convert Assertions.h to base/ equivalents (https://docs.google.com/spreadsheets/d/1-OyE2MgypFI5B-GfqFGRLgPtpa_aBaFC_uyh9...), but I don't see an equivalent for OOM_CRASH in base. Although perhaps there is one that I just didn't see. I need OOM_CRASH (and hence IMMEDIATE_CRASH, or equivalent) to move PartitionAlloc to base, but people really object to OOM_CRASH in base I can change PartitionAlloc to use some other kind of crash. But I'd rather stick with OOM_CRASH since it seems to be part of how we understand stack traces/crashes, at least for Windows. danakj, thoughts?
https://codereview.chromium.org/2525723004/diff/1/base/logging.h File base/logging.h (right): https://codereview.chromium.org/2525723004/diff/1/base/logging.h#newcode482 base/logging.h:482: #define LOGGING_CRASH() IMMEDIATE_CRASH() Just remove this and use IMMEDIATE_CRASH below?
https://codereview.chromium.org/2525723004/diff/1/base/logging.h File base/logging.h (right): https://codereview.chromium.org/2525723004/diff/1/base/logging.h#newcode482 base/logging.h:482: #define LOGGING_CRASH() IMMEDIATE_CRASH() > Just remove this and use IMMEDIATE_CRASH below? Done.
Thanks.. one more question https://codereview.chromium.org/2525723004/diff/20001/base/logging.h File base/logging.h (right): https://codereview.chromium.org/2525723004/diff/20001/base/logging.h#newcode449 base/logging.h:449: #ifndef IMMEDIATE_CRASH Why the #ifndef? https://codereview.chromium.org/2525723004/diff/20001/base/logging.h#newcode459 base/logging.h:459: #ifndef OOM_CRASH same. is there some collision that this is worrying about and we use some other macro instead? this looks highly confusing but i suspect is not needed?
https://codereview.chromium.org/2525723004/diff/20001/base/logging.h File base/logging.h (right): https://codereview.chromium.org/2525723004/diff/20001/base/logging.h#newcode449 base/logging.h:449: #ifndef IMMEDIATE_CRASH > Why the #ifndef? It's only there because it was in the original Blink version. I'm happy to remove it.
Thanks, LGTM w/ 1 more thing https://codereview.chromium.org/2525723004/diff/40001/base/logging.h File base/logging.h (left): https://codereview.chromium.org/2525723004/diff/40001/base/logging.h#oldcode457 base/logging.h:457: // Make all CHECK functions discard their log strings to reduce code This comment is still relevant, it is commenting on CHECK() below, so we should keep the comment here.
https://codereview.chromium.org/2525723004/diff/40001/base/logging.h File base/logging.h (left): https://codereview.chromium.org/2525723004/diff/40001/base/logging.h#oldcode457 base/logging.h:457: // Make all CHECK functions discard their log strings to reduce code > This comment is still relevant, it is commenting on CHECK() below, so we should keep the comment here. Argh, oops. Fixed.
The CQ bit was checked by palmer@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from yutak@chromium.org, danakj@chromium.org Link to the patchset: https://codereview.chromium.org/2525723004/#ps60001 (title: "Restore the necessary comment.")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
https://codereview.chromium.org/2525723004/diff/60001/base/logging.h File base/logging.h (right): https://codereview.chromium.org/2525723004/diff/60001/base/logging.h#newcode467 base/logging.h:467: // Make all CHECK functions discard their log strings to reduce code bloat, and Heh, sorry. Keep this inside the OFFICIAL_BUILD ifdef where it is true please :)
The CQ bit was unchecked by danakj@chromium.org
https://codereview.chromium.org/2525723004/diff/60001/base/logging.h File base/logging.h (right): https://codereview.chromium.org/2525723004/diff/60001/base/logging.h#newcode467 base/logging.h:467: // Make all CHECK functions discard their log strings to reduce code bloat, and > Heh, sorry. Keep this inside the OFFICIAL_BUILD ifdef where it is true please :) Done.
The CQ bit was checked by palmer@chromium.org
The patchset sent to the CQ was uploaded after l-g-t-m from danakj@chromium.org, yutak@chromium.org Link to the patchset: https://codereview.chromium.org/2525723004/#ps80001 (title: "Everything in its right place.")
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Thanks :) LGTM
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: mac_chromium_rel_ng on master.tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)
The CQ bit was checked by palmer@chromium.org
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: linux_chromium_chromeos_ozone_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
The CQ bit was checked by palmer@chromium.org
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: linux_chromium_asan_rel_ng on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
Message was sent while issue was closed.
Description was changed from ========== Move IMMEDIATE_CRASH and OOM_CRASH from wtf to base. Part of the WTF Headers Audit, and needed for moving PartitionAllocator to base. BUG=632441 ========== to ========== Move IMMEDIATE_CRASH and OOM_CRASH from wtf to base. Part of the WTF Headers Audit, and needed for moving PartitionAllocator to base. BUG=632441 R=danakj@chromium.org, yutak@chromium.org Committed: https://crrev.com/61343b095788170874ce18d6ffd86963cba14141 Cr-Commit-Position: refs/heads/master@{#435077} ==========
Message was sent while issue was closed.
Patchset 5 (id:??) landed as https://crrev.com/61343b095788170874ce18d6ffd86963cba14141 Cr-Commit-Position: refs/heads/master@{#435077}
Message was sent while issue was closed.
Description was changed from ========== Move IMMEDIATE_CRASH and OOM_CRASH from wtf to base. Part of the WTF Headers Audit, and needed for moving PartitionAllocator to base. BUG=632441 R=danakj@chromium.org, yutak@chromium.org Committed: https://crrev.com/61343b095788170874ce18d6ffd86963cba14141 Cr-Commit-Position: refs/heads/master@{#435077} ========== to ========== Move IMMEDIATE_CRASH and OOM_CRASH from wtf to base. Part of the WTF Headers Audit, and needed for moving PartitionAllocator to base. BUG=632441 R=danakj@chromium.org, yutak@chromium.org ==========
Message was sent while issue was closed.
Committed patchset #5 (id:80001) to pending queue manually as 511e3320f65b56d34d33e08270b85e92099dd809 (presubmit successful). |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
