From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14357 invoked by alias); 27 Aug 2014 21:58:28 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 14341 invoked by uid 89); 27 Aug 2014 21:58:27 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 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 (AES256-GCM-SHA384 encrypted) ESMTPS; Wed, 27 Aug 2014 21:58:27 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s7RLwNpP009268 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 27 Aug 2014 17:58:23 -0400 Received: from [127.0.0.1] (ovpn01.gateway.prod.ext.ams2.redhat.com [10.39.146.11]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id s7RLwLSa001603; Wed, 27 Aug 2014 17:58:22 -0400 Message-ID: <53FE547C.3030701@redhat.com> Date: Wed, 27 Aug 2014 21:58:00 -0000 From: Pedro Alves User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.7.0 MIME-Version: 1.0 To: Yao Qi , Peng Fan CC: "gdb@sourceware.org" Subject: Re: GDB Remote debug: Why several "$Z0,address,length" msg when only set one breakpoint? References: <53FC2FC1.9080600@gmail.com> <87mwaqixh2.fsf@codesourcery.com> <53FD8D31.9010507@gmail.com> <87d2bmgmil.fsf@codesourcery.com> In-Reply-To: <87d2bmgmil.fsf@codesourcery.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2014-08/txt/msg00131.txt.bz2 On 08/27/2014 01:11 PM, Yao Qi wrote: > GDB is interested in entry address, but I don't know why GDB insert > breakpoint there. In GDB, command 'maintenance info breakpoints' can > list all the user breakpoints and internal breakpoints. If it still > doesn't help, you can debug your gdb, set breakpoint > remote_insert_breakpoint, and check why the breakpoint is inserted at > 0x87800000. I'd guess this is a build of GDB targeting Linux, and then that breakpoint is the solib-event breakpoint. One of the last-resort addresses solib-svr4.c tries is _start: static const char * const bkpt_names[] = { "_start", ... Thanks, Pedro Alves