mandiant / mandiant/gocrack

"Double free or corruption" Error

Open
#63 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
1.3k
Forks
238
PR merge metrics
No merged PRs in 30d

Description

Has someone seen this problem before? I have fixed a lot of errors before but I can't find the solution to this one...
I attach a screenshot of the full output.

![Output](https://user-images.githubusercontent.com/58190928/80618485-bc035b80-8a43-11ea-892a-2f4d775d3f52.png)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, commands, or entry points; start by recovering the exact reproduction details from the screenshot and the GoCrack operation that triggers the error. Done means the cause is identified, the reported corruption error no longer occurs for that reproduction, and a regression check covers it.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
tooling
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.