8000 [BUG] incorrect work · Issue #12 · sectordistrict/intentrace · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[BUG] incorrect work #12

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and 8000 the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
titov32 opened this issue Mar 20, 2025 · 3 comments
Open

[BUG] incorrect work #12

titov32 opened this issue Mar 20, 2025 · 3 comments

Comments

@titov32
Copy link
titov32 commented Mar 20, 2025

When I investigate programs that continue to run until you stop them, the program output is displayed in the console or in a separate stream. If I send a SigStop (Ctrl + Z), the program keeps running in the background. Example: intentrace top. If I run a program that ends with a Segmentation Fault, it also runs, but there is no output from intentrace at all.

@sectordistrict
Copy link
Owner

I tested with both btop and top, intentrace behaves the same way that strace does with both top & btop exiting on CTRL-Z.

My guess is that top's output -which reports its own instance in the process list- might have confused you into thinking it was the instance that was traced by intentrace, can you try again and confirm if that was the case?

As for the segfault variant, I'll keep this issue open until that's also been tested.

@titov32
Copy link
Author
titov32 commented Mar 24, 2025

Sorry, problem is exist when send SigInt(Ctrl + C). The behavior is similar to running the command ping 8.8.8.8 & where the program's output continues to appear in the console, but I'm unable to send Ctrl + C. I can only stop the ping command by saying fg and then sending Ctrl + C. The difference with intentrace is that I can't say fg to bring it to the foreground.

@sectordistrict
Copy link
Owner

I tested again, and this seems to be what happening:

  • the shell redirects stdout from strace, but fails to do so with intentrace (they should be similar)
  • fg works for both strace and intentrace (tested on multiple terminals)
  • fg and then CTRL-C works on intentrace (also tested on multiple terminals)

I tested this by running intentrace long-running-command&

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants
0