Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and 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

Impossible to see stderr and stdout of release builds on Windows #578

Open
1 task done
GyulyVGC opened this issue Aug 2, 2024 · 1 comment
Open
1 task done
Assignees
Labels
Windows Something related to Windows operating system
Milestone

Comments

@GyulyVGC
Copy link
Owner

GyulyVGC commented Aug 2, 2024

Is there an existing issue for this?

  • I have searched the existing issues.

What's the problem?

I set the configuration attribute windows-subsystem="windows" for Windows release builds to avoid having a terminal running alongside Sniffnet when opening the app by clicking on its icon.

However, this prevents users to see stderr and stdout even when launching the app from terminal; in case of errors, this doesn't allow to see a trace of the problem, making debug more difficult.

Additional context

A possible solution that comes to my mind is to redirect stdout and stderr to a new file in the app's configuration directory.

@GyulyVGC GyulyVGC added the Windows Something related to Windows operating system label Aug 2, 2024
@GyulyVGC GyulyVGC added this to the v1.3.2 milestone Aug 2, 2024
@GyulyVGC GyulyVGC self-assigned this Aug 2, 2024
@T-256
Copy link

T-256 commented Oct 15, 2024

try: sniffnet.exe | more

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

No branches or pull requests

2 participants