gdb - debugging with piped input (not arguments)

gdb pipe
mandreko picture mandreko · Dec 7, 2011 · Viewed 45.9k times · Source

I typically run my program with:

perl -e 'print "A"x200' | ./vuln_prog

The stdin is consumed by a gets() function in C++.

If this were just a command argument, I could open gdb by doing:

gdb ./vuln_prog
run $(perl -e 'print "A"x200')

However, my scenario is not a command argument, but rather input (STDIN?). How would I debug this in gdb? I've tried a bunch of options, but nothing seems to really work.

I would normally just run gdb on the process, and when it prompts for user input, type it in, however I'm not wanting to type just "A". I want to type all chars from \x00-\xff, which I can't type.

Answer

zed_0xff picture zed_0xff · Dec 7, 2011 
gdb ./vuln_prog
run < filename_with_input

Related questions

Core dump file analysis

What are all the things I will need to check while analyzing a core dump file? Please tell me from scratch.

Read More
How do I analyze a program's core dump file with GDB when it has command-line parameters?

My program operates like this: exe -p param1 -i param2 -o param3 It crashed and generated a core dump file, core.pid. I want to analyze the core dump file by gdb ./exe -p param1 -i param2 -o param3 core.…

Read More
How do I run a program with commandline arguments using GDB within a Bash script?

When running a program on GDB, usually, the arguments for the program are given at the run command. Is there a way to run the program using GDB and as well as give arguments within a shell script? I saw …

Read More