gdb/2022: gdb hangs on command kill on Solaris10 edition 10/05

[steve at telxio dot com]

>Number:         2022
>Category:       gdb
>Synopsis:       gdb hangs on command kill on Solaris10 edition 10/05
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Oct 27 19:18:03 GMT 2005
>Closed-Date:
>Last-Modified:
>Originator:     Steve Williams
>Release:        gdb-6.3
>Organization:
>Environment:
sparc64-sun-solaris2.10 with 10_Recommended.zip patch cluster as of October 27, 2005 (which is the same as Solaris10 Edition 10/05)
>Description:
When gdb quits and tries to kill a process that is stopped, gdb hangs waiting for process to exit. The process is stopped and ignores the KILL signal.

A ctrl-C causes gdb to exit but, the process being debugged is left orphaned, a KILL -9 cleans it up.

Further searches on the SUN site confirm this is a known issue to Sun. They have a work around that involves issuing a command "prun <pid>" where pid is the pid of the debugged process. This puts the process in a run state, the signal is received and gdb exits normally.

See http://docs.sun.com/app/docs/doc/819-2423/6n4nbuduc?a=view

SUN issue number 6329593 (Problems With dbx and GNU Debuggers)
>How-To-Repeat:
Any ELF executable:
gdb <executable>
br main
r
q
>Fix:
in procfs.c in function proc_kill, why can't the function proc_run_process(pi, 0, signo) be called?

This would send the signal to the process and then start it running.
>Release-Note:
>Audit-Trail:
>Unformatted: