From: "Richard (sent by Nabble.com)" <lists@nabble.com>
To: gdb@sources.redhat.com
Subject: fork debugging : back to parent.
Date: Mon, 07 Aug 2006 20:21:00 -0000 [thread overview]
Message-ID: <5693501.post@talk.nabble.com> (raw)
Below is the code from "Advanced programming in the Unix environment". if I
set follow-fork to child, I can step ok to the exclp line. But how do I get
back to debugging the parent process? Is it possible? I tried setting
follow-fork back to "parent" and then "c"ontinuing but no joy. or do I have
to specifically save process ids and reattach to the parent process?
=======
#include "apue.h"
#include <sys/wait.h>
int
main(void)
{
char buf[MAXLINE]; /* from apue.h */
pid_t pid;
int status;
printf("%% "); /* print prompt (printf requires %% to print %) */
while (fgets(buf, MAXLINE, stdin) != NULL) {
if (buf[strlen(buf) - 1] == '\n')
buf[strlen(buf) - 1] = 0; /* replace newline with null */
if ((pid = fork()) < 0) {
err_sys("fork error");
} else if (pid == 0) { /* child */
execlp(buf, buf, (char *)0);
err_ret("couldn't execute: %s", buf);
exit(127);
}
/* parent */
if ((pid = waitpid(pid, &status, 0)) < 0)
err_sys("waitpid error");
printf("%% ");
}
exit(0);
}
--
View this message in context: http://www.nabble.com/fork-debugging-%3A-back-to-parent.-tf2067795.html#a5693501
Sent from the gdb - General forum at Nabble.com.
next reply other threads:[~2006-08-07 20:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-07 20:21 Richard (sent by Nabble.com) [this message]
2006-08-07 21:07 ` Daniel Jacobowitz
2006-08-07 21:47 ` Richard
2006-08-08 0:04 ` Daniel Jacobowitz
2006-08-08 7:27 ` Richard
2006-08-08 8:49 ` Richard
2006-08-08 13:16 ` Daniel Jacobowitz
2006-08-10 21:06 ` Richard
2006-08-10 21:39 ` Daniel Jacobowitz
2006-08-10 22:06 ` Richard
2006-08-10 22:10 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5693501.post@talk.nabble.com \
--to=lists@nabble.com \
--cc=gdb@sources.redhat.com \
--cc=rgrdev@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox