From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 457 invoked by alias); 12 Aug 2004 16:04:14 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 440 invoked from network); 12 Aug 2004 16:04:13 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 12 Aug 2004 16:04:13 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.10/8.12.10) with ESMTP id i7CG4Ce3019327 for ; Thu, 12 Aug 2004 12:04:13 -0400 Received: from localhost.redhat.com (porkchop.devel.redhat.com [172.16.58.2]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id i7CG3va16078; Thu, 12 Aug 2004 12:04:07 -0400 Received: from gnu.org (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id D58E02B9D; Thu, 12 Aug 2004 12:03:45 -0400 (EDT) Message-ID: <411B94E1.30803@gnu.org> Date: Thu, 12 Aug 2004 16:04:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-GB; rv:1.4.1) Gecko/20040801 MIME-Version: 1.0 To: Manoj Iyer Cc: gilliam@us.ibm.com, gdb-patches@sources.redhat.com Subject: Re: [RFC] New thread testcase. References: <4117F82B.nail1N111PN0T@mindspring.com> <41187827.nailB8H1E9AWV@mindspring.com> <4118E61B.3060902@gnu.org> <411930DF.30401@gnu.org> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-08/txt/msg00463.txt.bz2 > oh! sorry abt that... got confused btwn 'bugs'... > > The kernel bug was causing gdb to fail when passing a 32bit address to the > kernel. this was causing 32 bit gdb to fail in linux_test_for_tracefork() > by always returning second_pid = 0 in the PTRACE_GETEVENTMSG call. > > this resulted in linux_enable_event_reporting() not setting the PTRACE > fork options for the pid and then the thread never received a SIGSTOP. > > John Engel, kernel developer, debugged and fixed this problem in the > kernel after we reported this GDB problem to him... > > So, when you debug a multi-threaded app with 32bit GDB on a PPC64 system, > and you set a break point at the thread function and tried to step, you > get the message "reading register pc (#64): No such process." for example: Ewww! Yes, very good test, should have exercised this [not so] edge case years ago. One tweak, can the sleep(100) be avoided, instead using synchronization primatives? That way its clear that the test runs at full speed. Andrew