qilingframework / qilingframework/qiling

golang time.Sleep error

Open
#1,283 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
6.1k
Forks
798
Avg merge
1d 1h
Merged PRs (30d)
9

Description

*Describe the bug
A clear and concise description of what the bug is.
golang time.Sleep error
Sample Code

	fmt.Println("xxx")
	time.Sleep(time.Second * 5)
	fmt.Println("uuuuu")
    print(qiling.__version__)
    ql = Qiling(
        ["rootfs/x8664_linux/bin/sleep_hello"],
        "rootfs/x8664_linux",
        archtype = 'x8664',
        ostype='linux',
        verbose=QL_VERBOSE.DEFAULT,
        multithread=True,
        profile='netgear.ql',
        console=True
    )
    ql.run()

Expected behavior
A clear and concise description of what you expected to happen.
sleep(5000)

Screenshots
If applicable, add screenshots to help explain your problem.
image

Additional context
Add any other context about the problem here.

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

Reproduce the report with the Go sample and the Python Qiling setup shown in the issue, using rootfs/x8664_linux/bin/sleep_hello and ql.run(). No source file or test is named, so begin by tracing the observed time.Sleep behavior in this emulation setup. Done means the program waits for the expected 5000 milliseconds and then prints the later message.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, python
Domain
operating-systems, reverse-engineering
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.