summaryrefslogtreecommitdiffstats
path: root/sql/sql.gyp
diff options
context:
space:
mode:
authorssid <ssid@chromium.org>2016-01-13 06:21:57 -0800
committerCommit bot <commit-bot@chromium.org>2016-01-13 14:23:13 +0000
commit3be5b1ecdf66f6eaaa0ba98f9b36cc2d93bf54d9 (patch)
tree20326a0c236d72a2e28b007f1782116cf301b07c /sql/sql.gyp
parent3a6f49f649c3c413ca10fc60ec85f39532ac9e45 (diff)
downloadchromium_src-3be5b1ecdf66f6eaaa0ba98f9b36cc2d93bf54d9.zip
chromium_src-3be5b1ecdf66f6eaaa0ba98f9b36cc2d93bf54d9.tar.gz
chromium_src-3be5b1ecdf66f6eaaa0ba98f9b36cc2d93bf54d9.tar.bz2
[tracing] Add separate dump provider for sql connection
The sql connection memory dump is not thread safe since the connections can get deleted while a dump is happening. To make this thread safe, this CL introduces a dump provider class owned by the connection. This class holds a lock when dumping and deleting the database. Also, to workaround thread safe dump provider registration, it uses the UnregisterAndDeleteDumpProviderAsync api added in crrev.com/1430073002. BUG=466141 Review URL: https://codereview.chromium.org/1434993002 Cr-Commit-Position: refs/heads/master@{#369161}
Diffstat (limited to 'sql/sql.gyp')
-rw-r--r--sql/sql.gyp2
1 files changed, 2 insertions, 0 deletions
diff --git a/sql/sql.gyp b/sql/sql.gyp
index 362597e..2e02427 100644
--- a/sql/sql.gyp
+++ b/sql/sql.gyp
@@ -22,6 +22,8 @@
'sources': [
'connection.cc',
'connection.h',
+ 'connection_memory_dump_provider.cc',
+ 'connection_memory_dump_provider.h',
'error_delegate_util.cc',
'error_delegate_util.h',
'init_status.h',