From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15349 invoked by alias); 28 Jul 2005 04:24:25 -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 15318 invoked by uid 22791); 28 Jul 2005 04:24:22 -0000 Received: from ihemail1.lucent.com (HELO ihemail1.lucent.com) (192.11.222.161) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Thu, 28 Jul 2005 04:24:22 +0000 Received: from ihgp.ih.lucent.com (h135-1-218-100.lucent.com [135.1.218.100]) by ihemail1.lucent.com (8.12.11/8.12.11) with ESMTP id j6S4Ncav014655; Wed, 27 Jul 2005 23:23:39 -0500 (CDT) Received: from [192.11.173.51] by ihgp.ih.lucent.com (8.11.6+Sun/EMS-1.5 sol2) id j6S4Nc218704; Wed, 27 Jul 2005 23:23:38 -0500 (CDT) Message-ID: <42E85DC9.6040107@lucent.com> Date: Thu, 28 Jul 2005 04:24:00 -0000 From: Dave Trollope User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax) MIME-Version: 1.0 To: Daniel Jacobowitz CC: "Cuthbertson, Reva D." , gdb@sources.redhat.com Subject: Re: Question regarding setting breakpoints on 'C' labels and the handling of DW_TAG_label in new_symbol() in dwarf2read.c. References: <20050624031916.GA17083@nevyn.them.org> In-Reply-To: <20050624031916.GA17083@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2005-07/txt/msg00261.txt.bz2 I too tried this recently and was disappointed to find it didn't work. Heres why I was trying it: We have a number of source trees where code changes regularly. By using a label, we can write generic breakpoint scripts that are source tree independant (I.E. Don't need line numbers to place the breakpoint. etc). Is there an alternative way to do what we are trying to achieve? Cheers Dave Daniel Jacobowitz wrote: >On Thu, Jun 23, 2005 at 04:56:15PM -0700, Cuthbertson, Reva D. wrote: > > >>Hello, >> >>I was trying to set a breakpoint on a 'C' label in gdb and when I could >>not do it I tried to find out why. I noticed a few things and had a few >>questions. >> >> > >Simply, GDB does not support this. It may have once upon a time, but >no one has used the feature for years. > > > >