Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Tracking down bugs #331

Copy link
Copy link
@mcollina

Description

@mcollina
Issue body actions

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.

Reactions are currently unavailable

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

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.