From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32185 invoked by alias); 25 Sep 2011 10:18:23 -0000 Received: (qmail 32175 invoked by uid 22791); 25 Sep 2011 10:18:22 -0000 X-SWARE-Spam-Status: No, hits=-5.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from smtp.checkpoint.com (HELO michael.checkpoint.com) (194.29.34.68) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 25 Sep 2011 10:18:06 +0000 X-CheckPoint: {4E7F0CE9-7-1B221DC2-FFFF} Received: from il-ex01.ad.checkpoint.com (il-ex01.ad.checkpoint.com [194.29.34.26]) by michael.checkpoint.com (8.13.8/8.13.8) with ESMTP id p8PAHpYb001533; Sun, 25 Sep 2011 13:17:51 +0300 Received: from il-ex03.ad.checkpoint.com (194.29.34.71) by il-ex01.ad.checkpoint.com (194.29.34.26) with Microsoft SMTP Server (TLS) id 8.2.255.0; Sun, 25 Sep 2011 13:17:51 +0300 Received: from il-ex01.ad.checkpoint.com ([126.0.0.2]) by il-ex03.ad.checkpoint.com ([194.29.34.71]) with mapi; Sun, 25 Sep 2011 13:17:51 +0300 From: Avi Gozlan To: Avi Gozlan , "'Tom Tromey'" , "'gdb-patches@sourceware.org'" CC: Matan Ben Gur Date: Sun, 25 Sep 2011 10:47:00 -0000 Subject: RE: Re: [RFC] canonical linespec and multiple breakpoints ... Message-ID: <9C4E85B61203CD419BB3A638E5F6833301E5CA98B661@il-ex01.ad.checkpoint.com> References: <9C4E85B61203CD419BB3A638E5F6833301E5CA98B64F@il-ex01.ad.checkpoint.com> In-Reply-To: <9C4E85B61203CD419BB3A638E5F6833301E5CA98B64F@il-ex01.ad.checkpoint.com> x-kse-antivirus-interceptor-info: scan successful x-kse-antivirus-info: Clean Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-KSE-AntiSpam-Interceptor-Info: protection disabled 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 X-SW-Source: 2011-09/txt/msg00440.txt.bz2 Any reference to the below issues would be appreciated. Thanks. -----Original Message----- From: Avi Gozlan=20 Sent: Sunday, September 18, 2011 1:22 PM To: 'Tom Tromey'; 'gdb-patches@sourceware.org' Cc: Avi Gozlan; Matan Ben Gur Subject: Re: [RFC] canonical linespec and multiple breakpoints ... Hello, On the basis of your proposal dealing with supporting multiple breakpoints and the discussion that followed it, I would like to raise some questions.= =20 These issues are highly relevant for our needs (the need was first described in bug 12313 in the GDB bug database). Among varying GDB uses, we use GDB to debug a process which loads (using=20 dlopen) the same exact library multiple times (in fact there are copies of the library otherwise dlopen returns the same handle for each load). We find your proposal very useful for us to be able to attach to the process and=20 debug a specific library. Though, we do have some questions and suggestions. Pardon technical inaccuracies in GDB terminology. 1) The proposal discusses function breakpoints. Will it also enable=20 inspecting global and static variables from a specific library? 2) Just to make sure we understand the interaction of the user interface=20 with "set multiple-symbols": it will be possible to request GDB for a=20 specific variable/function by a library name without getting it from all libraries or get a question (ask) each time, right? Otherwise it will be very inconvenient to inspect multiple variables within a given library. 3) Will the library specific interface know how to handle non-stripped=20 libraries that are compiled without debug information (no "-g")? 4) We suggest adding an option to enable the GDB backtrace command to=20 show the library name for each function. In our usage case we have=20 scenarios in which the libraries interact with each other and a backtrace=20 showing the library name for each function can enable us understand the=20 interaction perfectly. 5) Perhaps a little pedantic but what about handling symbols with=20 different names in libraries with identical name which lie in different=20 paths? Thanks, Avi