Debugging child process after fork (follow-fork-mode child configured)

by

The child process inherits signal handlers from the parent, but not the pending signal.

After forking try installing the signal handler for SIGTRAP at a place in code where the child process executes after forking. If you don’t handle SIGTRAP, the default action is that the child is terminated.

If you want to debug the child process, you must use follow-fork-mode.
You must set the mode using

set follow-fork-mode child

However, now only the child can be debugged, and the parent runs unchecked.

There is an alternative way of debugging the child process.

After fork() is executed, put a sleep() call in the code where the child executes, get the PID of the child using the ps utility, then attach the PID.

attach <PID of child process>

Now, you can debug the child process, like any other process.

After debugging, you can detach the PID using

detach

More Related Contents:

  1. How do I debug the child process after fork() in gdb?
  2. what the output of this code and why?
  3. How to Raise SIGTERM in Windows [closed]
  4. How to make child process die after parent exits?
  5. How to share memory between processes created by fork()?
  6. Differences between fork and exec
  7. How to capture Control+D signal?
  8. Working of fork() in linux gcc [duplicate]
  9. Grabbing output from exec
  10. How can I tell if a library was compiled with -g?
  11. Is it possible to “jump”/”skip” in GDB debugger?
  12. How to use POSIX semaphores on forked processes in C?
  13. gdb – debugging with pipe
  14. Are file descriptors shared when fork()ing?
  15. How to solve “ptrace operation not permitted” when trying to attach GDB to a process?
  16. How does sig_atomic_t actually work?
  17. Cannot insert breakpoints. Addresses with low values
  18. Simple Signals – C programming and alarm function
  19. How to make parent wait for all child processes to finish?
  20. Why does gdb evaluate sqrt(3) to 0?
  21. How do I pass a command line argument while starting up GDB in Linux? [duplicate]
  22. How to modify memory contents using GDB?
  23. segfault only when NOT using debugger
  24. Which thread handles the signal?
  25. Signal queuing in C
  26. Can’t step into string.h function with GDB
  27. C – Retrieving a child’s exit status that is larger than 8 bits
  28. longjmp() from signal handler
  29. What exactly is -fno-builtin doing here?
  30. Why can’t I ignore SIGSEGV signal?

Leave a Comment