gdb – debugging with pipe

by

At first, you may run the program and debug it by pid. This solution, of course, doesn’t cover all cases.

Another approach is to use Linux capabilities for inter-process communication. In short, you redirect the output of ret to a FIFO special file (“named pipe”) and then read from that FIFO via debugger. Here’s how it’s done. From bash, run:

mkfifo foo

This creates a special file in your directory that will serve as a named pipe. When you write text to this file (using the same syntax echo "Hello" >foo), the writing program will block until someone reads the data from the file (cat <foo, for instance). In our case, a gdb-controlled process will read from this file.

After you created a fifo, run from bash:

ret > foo &   # ampersand because it may block as nobody is reading from foo
gdb blah

Then, in gdb prompt, run

run <foo

And get the desired effect. Note that you can’t read the data from the fifo (as well as from a usual pipe) twice: when you’ve read all the data, the blah process dies and you should repeat the command writing to foo (you may do it from the other shell window).

When you’re done, remove the fifo with rm foo (or place it into the directory where it will automatically be removed upon system restart, such as /tmp).

More Related Contents:

  1. How to debug using gdb?
  2. Best way to invoke gdb from inside program to print its stacktrace?
  3. How can I tell if a library was compiled with -g?
  4. How to print every executed line in GDB automatically until a given breakpoint is reached?
  5. Include source code of malloc.c in gdb?
  6. Is it possible to “jump”/”skip” in GDB debugger?
  7. Printing all global variables/local variables?
  8. How to solve “ptrace operation not permitted” when trying to attach GDB to a process?
  9. Cannot insert breakpoints. Addresses with low values
  10. Why does gdb evaluate sqrt(3) to 0?
  11. How do I pass a command line argument while starting up GDB in Linux? [duplicate]
  12. How to modify memory contents using GDB?
  13. segfault only when NOT using debugger
  14. How do I print a #defined constant in GDB?
  15. How do I debug the child process after fork() in gdb?
  16. Can’t step into string.h function with GDB
  17. gdb gives strange output when using math.h functions [duplicate]
  18. Why GDB jumps unpredictably between lines and prints variables as “”?
  19. How to do an specific action when a certain breakpoint is hit in GDB?
  20. Program received signal SIGPIPE, Broken pipe
  21. Recommended way to track down array out-of-bound access/write in C program
  22. gdb prints wrong values when modifying arguments
  23. What exactly is -fno-builtin doing here?
  24. Debugging child process after fork (follow-fork-mode child configured)
  25. C – Counting Numbers {making a program} [closed]
  26. Real-world use of X-Macros
  27. Adding leading underscores to assembly symbols with GCC on Win32?
  28. Print an int in binary representation using C
  29. scanf not working as expected
  30. How to convert integer value to Roman numeral string?

Leave a Comment