FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

Tracking down bugs · Issue #331 · nodegit/nodegit · GitHub

Repository navigation

Tracking down bugs #331

Description

Given that the codebase is fairly complex, and the binaries are downloaded from S3, what is the process of tracking down a crash? I would love to get a debug build out of nodegit, but unfortunately I need some guidance, as I could not get it to build from sources (vs downloading the stuff from S3) to enable a debug build.

I am getting a laconic:

node(4971,0x7fff75082300) malloc: *** error for object 0x100c10fb0: pointer being freed was not allocated

This is a regression from 0.2.3.

Originally reported by @juliangruber in nearform/nscale#55.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions


      Back | FazBrowse Home | New Git URL