Date: Sun, 20 Feb 2005 19:15:01 -0600 (CST) From: Sean Farley <sean-freebsd@farley.org> To: FreeBSD-gnats-submit@FreeBSD.org Subject: gnu/77818: GDB locks in wait4() when running applications Message-ID: <200502210115.j1L1F1jK067881@thor.farley.org> Resent-Message-ID: <200502210120.j1L1KIAB024214@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 77818 >Category: gnu >Synopsis: GDB locks in wait4() when running applications >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Feb 21 01:20:17 GMT 2005 >Closed-Date: >Last-Modified: >Originator: Sean Farley >Release: FreeBSD 5.3-STABLE i386 >Organization: >Environment: System: FreeBSD thor.farley.org 5.3-STABLE FreeBSD 5.3-STABLE #0: Thu Feb 17 15:11:46 CST 2005 root@thor.farley.org:/usr/obj/usr/src/sys/THOR i386 >Description: Whenever I run an application through the system's GDB, GDB locks in wait4(). It does not matter if the application has debugging information or not. /bin/ls will lock GDB up for me until I type Ctrl-C. Two systems of mine exhibit this behavior. One has the binary nvidia driver with a lot of changes in libmap.conf. The other is headless without a libmap.conf. >How-To-Repeat: gdb /bin/ls >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200502210115.j1L1F1jK067881>