From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30642 invoked by alias); 12 Aug 2002 14:59:41 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 30627 invoked from network); 12 Aug 2002 14:59:39 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sources.redhat.com with SMTP; 12 Aug 2002 14:59:39 -0000 Received: from int-mx2.corp.redhat.com (nat-pool-rdu.redhat.com [172.16.52.200] (may be forged)) by mx1.redhat.com (8.11.6/8.11.6) with ESMTP id g7CEk7l28306 for ; Mon, 12 Aug 2002 10:46:07 -0400 Received: from potter.sfbay.redhat.com (potter.sfbay.redhat.com [172.16.27.15]) by int-mx2.corp.redhat.com (8.11.6/8.11.6) with ESMTP id g7CExau32638; Mon, 12 Aug 2002 10:59:37 -0400 Received: from romulus.sfbay.redhat.com (remus.sfbay.redhat.com [172.16.27.252]) by potter.sfbay.redhat.com (8.11.6/8.11.6) with ESMTP id g7CExZe10777; Mon, 12 Aug 2002 07:59:36 -0700 Received: (from kev@localhost) by romulus.sfbay.redhat.com (8.11.6/8.11.6) id g7CExWP31644; Mon, 12 Aug 2002 07:59:32 -0700 Date: Mon, 12 Aug 2002 07:59:00 -0000 From: Kevin Buettner Message-Id: <1020812145931.ZM31643@localhost.localdomain> In-Reply-To: Zheng Jian-Ming "about lin-lwp.c" (Aug 11, 11:52pm) References: <20020811155249.GA19815@cissol7.cis.nctu.edu.tw> To: Zheng Jian-Ming , gdb@sources.redhat.com Subject: Re: about lin-lwp.c MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2002-08/txt/msg00094.txt.bz2 On Aug 11, 11:52pm, Zheng Jian-Ming wrote: > I see this function "lin_lwp_resume()" in gdb/lin-lwp.c, but don't > know what "gdb_assert(signo == TARGET_SIGNAL_0)" to do. gdb_assert() generates an internal error if the condition in question does NOT hold. So for the above, an internal error will be generated if !(signo == TARGET_SIGNAL_0). Please note the exact context of this assertion. I.e, we have a wait status already associated with the thread. You should also read the FIXME just prior to the assert. > Does statement "iterate_over_lwps(resume_callback, NULL)" cause all > threads to resume? Yes. (Well, technically, it causes all LWPs to resume.) Kevin