DynamoRIO / DynamoRIO/dynamorio

ASSERT (64-bit Debug Linux GO) core/fragment.c:6329

Open
#1,053 1 comment 0 reactions 0 assignees View on GitHub
Migrated OpSys-Linux Priority-Low
Dominant language
C
Stars
3.2k
Forks
629
Avg merge
2d 18h
Merged PRs (30d)
30

Description

_From [zhao...@google.com](https://code.google.com/u/106321947286816917100/) on January 11, 2013 16:56:47_

> ~/Workspace/DynamoRIO/builds/build_x64_dbg.git/bin64/drrun -debug -- go run hello.go

<-- parent 12074 forked child 12088 -->
# command-line-arguments
<-- execve /home/zhaoqin/Workspace/Packages/GO/go/pkg/tool/linux_amd64/6g -->

<-- parent 12074 forked child 12089 -->

hang on running the build hello program:

> file hello
hello: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, not stripped

> ~/Workspace/DynamoRIO/builds/build_x64_dbg.git/bin64/drrun -debug -early -- ./hello

runtime: signal received on thread not created by Go.

_Original issue: http://code.google.com/p/dynamorio/issues/detail?id=1053_

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the failure with the reported drrun command against the Go hello program on 64-bit debug Linux. Read core/fragment.c at assertion line 6329 and compare the two reported execution paths. Done means the Go program runs without triggering the ASSERT or the related internal error.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, go, linux
Domain
devtools, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.