public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "mageofdancingdragons at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/17229] New: infinite loop in linux_check_ptrace_features
Date: Tue, 05 Aug 2014 16:53:00 -0000 [thread overview]
Message-ID: <bug-17229-4717@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=17229
Bug ID: 17229
Summary: infinite loop in linux_check_ptrace_features
Product: gdb
Version: 7.7
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: mageofdancingdragons at gmail dot com
In linux_check_ptrace_features there's an infinite loop possibility when the
child dies unexpectedly.
332 child_pid = linux_fork_to_function (NULL, linux_child_function);
333
334 ret = my_waitpid (child_pid, &status, 0);
After these two calls complete successfully, there is a child process, and the
value of status fulfills WIFSTOPPED(status).
Now the child process gets killed (for some reason or another).
Finally we hit the cleanup loop at the end:
349 do
350 {
351 ret = ptrace (PTRACE_KILL, child_pid, (PTRACE_TYPE_ARG3) 0,
352 (PTRACE_TYPE_ARG4) 0);
353 if (ret != 0)
354 warning (_("linux_check_ptrace_features: failed to kill child"));
355 my_waitpid (child_pid, &status, 0);
356 }
357 while (WIFSTOPPED (status));
both ptrace and my_waitpid should fail because the child_pid is no longer a
valid process, but the value of status never changes because waitpid is
returning an error.
The return value of waitpid should be checked and the loop exited if it fails
(with appropriate error reporting).
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2014-08-05 16:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 16:53 mageofdancingdragons at gmail dot com [this message]
2014-08-05 16:59 ` [Bug gdb/17229] " mageofdancingdragons at gmail dot com
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=bug-17229-4717@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=gdb-prs@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).