This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
Re: gdb/2022: gdb hangs on command kill on Solaris10 edition 10/05
- From: "Steve Williams" <steve dot williams at utstar dot com>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 10 Nov 2005 21:58:01 -0000
- Subject: Re: gdb/2022: gdb hangs on command kill on Solaris10 edition 10/05
- Reply-to: "Steve Williams" <steve dot williams at utstar dot com>
The following reply was made to PR gdb/2022; it has been noted by GNATS.
From: "Steve Williams" <steve.williams@utstar.com>
To: <gdb-gnats@sources.redhat.com>
Cc:
Subject: Re: gdb/2022: gdb hangs on command kill on Solaris10 edition 10/05
Date: Thu, 10 Nov 2005 13:52:54 -0800
The patch I posted had a problem, I forgot to remove the return when cutting
and pasting. The inferiors left hanging around after the testsuite run were
because I left a extra return in the code.
This patch supersedes the previous patch. This patch allows the inferior to
exit normally on a quit of gdb or an explicit kill. It also does not leave
orphaned inferiors hanging around either.
--- gdb-6.3/gdb/procfs.c 2005-11-10 13:51:21.884063000 -0800
+++ gdb-6.3p/gdb/procfs.c 2005-11-10 13:32:45.595699000 -0800
@@ -4736,6 +4736,11 @@
ioctl (pi->ctl_fd, PIOCSSIG, &newsiginfo);
}
#else /* PROCFS_NEED_PIOCSSIG_FOR_KILL */
+ if (proc_flags (pi) & (PR_STOPPED | PR_ISTOP))
+ {
+ if (!proc_run_process (pi, 0, 0))
+ proc_error (pi, "make_signal_thread_runnable", __LINE__);
+ }
if (!proc_kill (pi, SIGKILL))
proc_error (pi, "unconditionally_kill, proc_kill", __LINE__);
#endif /* PROCFS_NEED_PIOCSSIG_FOR_KILL */