You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This works without --break. When i try to --break, gdb instantly takes the input as commands (probably the remaining of input), and does quit out from the debugger.
Is there a way to keep the debugger alive, or to not parse the piped input as gdb commands?
Normaly there would be the run < input command in gdb, but this is not realy the value which would be provided by heaptrace breakpoints.
Thanks for your help
The text was updated successfully, but these errors were encountered:
Hello,
my program takes input via a pipe, for example:
cat input | heaptrace ./program
This works without --break. When i try to --break, gdb instantly takes the input as commands (probably the remaining of input), and does quit out from the debugger.
Is there a way to keep the debugger alive, or to not parse the piped input as gdb commands?
Normaly there would be the run < input command in gdb, but this is not realy the value which would be provided by heaptrace breakpoints.
Thanks for your help
The text was updated successfully, but these errors were encountered: