From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14281 invoked by alias); 5 Feb 2014 12:31:15 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 14271 invoked by uid 89); 5 Feb 2014 12:31:15 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 05 Feb 2014 12:31:14 +0000 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s15CVA8L001433 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 5 Feb 2014 07:31:11 -0500 Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.ams2.redhat.com [10.39.146.11]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id s15CV8Co009582; Wed, 5 Feb 2014 07:31:09 -0500 Message-ID: <52F22F0C.9010901@redhat.com> Date: Wed, 05 Feb 2014 12:31:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7 MIME-Version: 1.0 To: Yao Qi CC: gdb-patches@sourceware.org, marc.khouzam@ericsson.com Subject: Re: [PATCH 0/2] Create inferior fro trace file target References: <1391060652-10870-1-git-send-email-yao@codesourcery.com> <52F15433.5070305@redhat.com> <52F22B49.2050802@codesourcery.com> In-Reply-To: <52F22B49.2050802@codesourcery.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2014-02/txt/msg00036.txt.bz2 On 02/05/2014 12:15 PM, Yao Qi wrote: >> > We've moved in the direction of "always a thread" a while ago, > What is "always a thread"? Can you elaborate? "info threads" used to come out empty until a second thread showed up. Here's 6.8 debugging a single-threaded program: (gdb) info threads (gdb) info program Using the running image of child process 12775. Program stopped at 0x4004cf. It stopped at a breakpoint that has since been deleted. (gdb) vs 7.0/current mainline: (gdb) info threads Id Target Id Frame * 1 process 12748 "main" main (argc=1, argv=0x7fffffffdb18) at main.c:5 (gdb) Basically, GDB nowadays models non-threaded programs as single-threaded programs. Thus "always a(t least one) thread". -- Pedro Alves