Currently, the main source of truth of crash keys resides in //chrome/common/crash_keys.cc (specifically, in crash_keys::RegisterChromeCrashKeys()). All sorts of keys are stuffed in there, including keys from //chrome, //media and //content.
To support projects that will use crash reporting but don't want to depend on //chrome, we should have each component that has crash keys define their own collections of keys. I envision this as something where each component will return (or append to) a vector of base::debug::CrashKeys that are used in that directory hierarchy. Proposed structure:
//content/common/crash_keys.{h,cc}
//media/base/crash_keys.{h,cc}
//chrome/common/crash_keys.{h,cc}
For a first pass (this issue), the cleanup will be limited to pulling apart the large crash key declaration currently in crash_keys::RegisterChromeCrashKeys().
(Some background reading: https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/2NVBSWHUAP0)
Comment 1 by sanfin@chromium.org
, Apr 13 2016