From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26822 invoked by alias); 14 Mar 2012 17:58:20 -0000 Received: (qmail 26814 invoked by uid 22791); 14 Mar 2012 17:58:19 -0000 X-SWARE-Spam-Status: No, hits=-2.7 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,RCVD_IN_DNSWL_LOW,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail-ee0-f41.google.com (HELO mail-ee0-f41.google.com) (74.125.83.41) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 14 Mar 2012 17:58:06 +0000 Received: by eeke53 with SMTP id e53so1312382eek.0 for ; Wed, 14 Mar 2012 10:58:05 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding:x-system-of-record :x-gm-message-state; bh=4AsczjcpOHDNrumICLTEql3mJIgFm+9MXKgvDwq0DYg=; b=BaTKs30K2mJAJMJVRWYS3sKSNsRC70Z6E3m0vWTnkqHHkklODWQ8N29O61d8PJJ5YI gWLT22t+UH6m9DkDbzQU5s/JgtEVxLZOnpg/R59EdPJCI7mbltlSVD4WfD+nPbX9bfX7 PhXb3u8kjfljScxSAJINZV2vihnQJgYngvMCFSA/6p5cgMm1BsNL9IGoKzf3LhlKCFFo 43RMY4pV0+yFtDNDL09pskz6ctrxUV04thXWn077K3BegnBnmDfeinbp5cCe95d13SCk 7QDIcQ3gdm/SjZYMKeLm+xQFyevvVNvj16Mt3an6Y4rlfADghQwk0jGo9ECXiPQ8jSRg aHsA== Received: by 10.52.240.161 with SMTP id wb1mr2645774vdc.20.1331747884750; Wed, 14 Mar 2012 10:58:04 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.240.161 with SMTP id wb1mr2645757vdc.20.1331747884570; Wed, 14 Mar 2012 10:58:04 -0700 (PDT) Received: by 10.220.187.12 with HTTP; Wed, 14 Mar 2012 10:58:04 -0700 (PDT) In-Reply-To: <20120314175451.GA20072@host2.jankratochvil.net> References: <20120314133746.GA5696@redhat.com> <20120314175451.GA20072@host2.jankratochvil.net> Date: Wed, 14 Mar 2012 17:58:00 -0000 Message-ID: Subject: Re: [RFA take 6] Allow setting breakpoints on inline functions (PR 10738) From: Doug Evans To: Jan Kratochvil Cc: gdb-patches@sourceware.org, Eli Zaretskii , Mark Wielaard , gbenson@redhat.com Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-System-Of-Record: true X-Gm-Message-State: ALoCoQmVxau9uBv81/FeXSGqblZJjLT9DySz01tNwHSrVDHSrecjNyRT8XScHSNVnTD00HGCJ95I9JadGEAUboU0rwjQgVdh02Kk8y5yf7fPsG9AsKaJcbY8hmoLslXG/9ZUOF3lkz1w6xbKkiUM5yc4muncG5/TMA== X-IsSubscribed: yes 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: 2012-03/txt/msg00496.txt.bz2 On Wed, Mar 14, 2012 at 10:54 AM, Jan Kratochvil wrote: > On Wed, 14 Mar 2012 18:50:55 +0100, Doug Evans wrote: >> + =A0--use-old-index-sections\n\ >> + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Do not reject old (broken) .gd= b_index sections.\n\ >> +"), stream); >> >> s/(broken)/(incomplete)/ > > FYI I may not have the right interpretation of English words but with > "incomplete" it may suggest to me that only part of the file will use ind= ex > and part of the file will be processed by a slower non-indexed method. > > It should suggest user the GDB functionality will be affected. The doc patch uses the word "incomplete", so that's why I suggest using it = here. If one wants to find a better word, great, but I think the same word should be used in both places.