-
Notifications
You must be signed in to change notification settings - Fork 9
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
Add convienient way for passing data to stdin #22
Comments
Sorry for taking so long to respond. I've been quite busy with work
lately.
In general I like the idea and see how it would be useful to something
to stdin via a script or something. I wonder about the best way to that,
though. Consider that you might want to restart the debugging session
after you've stepped over a critical function. When restarting the
execution the program would possibly miss some part of the data passed
via stdin.
What do you think about passing a script via commandline argument that
would be executed to the program whenever it is started? Something like
this
```console
$ ugdb --stdin-script script.sh ./some-exec
```
where script.sh contains `cat redirected_file.txt` or `printf
"some-string\ndupa\n"`?
|
Also sorry for taking so long to respond. I've had misconfigured github notfications.
Good point, I missed that.
$ ugdb --stdin-script script.sh ./some-exec
Sounds good. If you pass $ ugdb --stdin-script "curl something | tail" ./some-exec |
Let's say i have prog which reads data from stdin
I run it using my shell's input redirection:
It would be nice if ugdb took stdin and passed it to debugged program so we could use it that way:
The text was updated successfully, but these errors were encountered: