Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(183)

Issue 2843023: Avoid a potential null dereference wrt the CPU profiler.... (Closed)

Created:
10 years, 6 months ago by zarko
Modified:
9 years, 7 months ago
CC:
v8-dev, Vitaly Repeshko, Dmitry Titov
Visibility:
Public.

Description

Avoid a potential null dereference wrt the CPU profiler. GetActiveProfilerModules()/PauseProfiler()/ResumeProfiler() can be reached from the API when the --prof runtime flag is not set, leading to null dereferences. Verify that Logger::profiler_ is non-NULL before using it. Committed: http://code.google.com/p/v8/source/detail?r=4953

Patch Set 1 #

Total comments: 1
Unified diffs Side-by-side diffs Delta from patch set Stats (+5 lines, -5 lines) Patch
M src/log.cc View 4 chunks +5 lines, -5 lines 1 comment Download

Messages

Total messages: 2 (0 generated)
zarko
This is the patch for the Logger bug from http://codereview.chromium.org/2841023/show ported to bleeding_edge. Thanks Luke ...
10 years, 6 months ago (2010-06-24 23:13:21 UTC) #1
mnaganov (inactive)
10 years, 6 months ago (2010-06-25 09:14:56 UTC) #2
LGTM

On 2010/06/24 23:13:21, zarko wrote:
> This is the patch for the Logger bug from
> http://codereview.chromium.org/2841023/show ported to bleeding_edge.
> 
> Thanks
>   Luke
> 
> http://codereview.chromium.org/2843023/diff/1/2
> File src/log.cc (right):
> 
> http://codereview.chromium.org/2843023/diff/1/2#newcode310
> src/log.cc:310: void Profiler::Run() {
> Would it be helpful to ASSERT(Logger::profiler_ == this)?

Powered by Google App Engine
This is Rietveld 408576698