Currently, we store the breakpad revision that stackwalker uses in build-breakpad.sh, build it using a TaskCluster script, and then upload the build to a single public URL. Because of this, we cannot build a new revision of Breakpad in TaskCluster without making it the version we're using. Instead, we should be publishing Breakpad builds to a URL that includes the revision we're building from, so that we can pin stackwalker builds to a specific breakpad version and update it independently from Breakpad builds.  https://github.com/mozilla-services/socorro/blob/052d90bb2e94f581e61fae6c32c4aa523ad8d496/scripts/build-breakpad.sh#L17  https://github.com/mozilla-services/socorro/blob/052d90bb2e94f581e61fae6c32c4aa523ad8d496/scripts/breakpad-taskcluster.sh#L22  https://index.taskcluster.net/v1/task/project.socorro.breakpad.v1.builds.linux64.latest/artifacts/public/breakpad.tar.gz
While we're at it, we should update the set_up_stackwalk.sh script used in the Docker images to build Breakpad if the pinned version hasn't been uploaded. That will let us run CI against new pinned versions before we run the TC build.  https://github.com/mozilla-services/socorro/blob/master/docker/set_up_stackwalk.sh
This is something we should get to because it fixes some issues we have when updating breakpad. Making this a P2.