Skip to main content

git-blame for stacktraces

Project description


git-stacktrace is designed to make it easy to figure out which commit caused a given stacktrace.

git-stacktrace looks for:

  • commits in given range that touched files in the stacktrace

  • commits in given range that added/removed code present the stacktrace

Supported Languages

  • Python

  • Java


Run tests with: tox


$ pip install git_stacktrace


For the CLI see: git stacktrace -h

For the Python API see: git_stacktrace/


Example output:

$ git stacktrace < trace
Traceback (most recent call last):
 File "webapp/framework/", line 72, in _call
   result = getattr(self, method_name)()
 File "webapp/resources/", line 232, in get
   if self.options['from_navigate'] == "true":

commit da39a3ee5e6b4b0d3255bfef95601890afd80709
Commit Date: Tue, 19 Jul 2016 14:18:08 -0700
Author:      John Doe <>
Subject:     break interest resource
Files Modified:
   - webapp/resources/
Lines Added:
   - "if self.options['from_navigate'] == "true":"



  • Match file line numbers in stacktrace to lines changed in commits

  • Differentiate files added, deleted and modified

  • print stacktrace headers and footers

  • Fix git pickaxe error (Use ‘–’ to separate paths from revisions)

  • Add initial java stacktrace support. Begin supporting basic java stacktraces, some more complex formats are not supported yet.


  • Get ready for pypi


  • Initial open source commit

Project details

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

git-stacktrace-0.5.tar.gz (18.4 kB view hashes)

Uploaded Source

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page