This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/17229] New: infinite loop in linux_check_ptrace_features
- From: "mageofdancingdragons at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Tue, 05 Aug 2014 16:53:26 +0000
- Subject: [Bug gdb/17229] New: infinite loop in linux_check_ptrace_features
- Auto-submitted: auto-generated
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.