From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4572 invoked by alias); 21 Mar 2012 15:41:51 -0000 Received: (qmail 4554 invoked by uid 22791); 21 Mar 2012 15:41:49 -0000 X-SWARE-Spam-Status: No, hits=-6.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 21 Mar 2012 15:41:23 +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 q2LFfLmd003962 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 21 Mar 2012 11:41:21 -0400 Received: from valrhona.uglyboxes.com (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id q2LFfHWc026639 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 21 Mar 2012 11:41:20 -0400 Message-ID: <4F69F69D.2080803@redhat.com> Date: Wed, 21 Mar 2012 15:41:00 -0000 From: Keith Seitz User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20120209 Thunderbird/10.0.1 MIME-Version: 1.0 To: Martin CC: gdb@sourceware.org Subject: Re: possible regression in gdb 7.4 with -break-insert +0 References: <4F69ED5D.1000006@mfriebe.de> In-Reply-To: <4F69ED5D.1000006@mfriebe.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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 X-SW-Source: 2012-03/txt/msg00056.txt.bz2 On 03/21/2012 08:01 AM, Martin wrote: > I believe I found a regression in gdb 7.4. (Tested on Win 32bit Vista) > > using "gdb -i mi", the command "-break-insert +0" should insert a > breakpoint at the an offset of 0 lines from current. > - With previous versions of gdb, if the command was issued before > -exec-run, then a breakpoint was inserted at the first line of code. > - With 7.4-2, it is inserted, but when running gives the error: > &"Error in re-setting breakpoint 1: No line 0 in file \"Test.pas\".\n" I can reproduce this with CVS HEAD today. I believe this is fallout from the ambiguous linespec patch, but I did not investigate it, because I've just submitted a monstrous patch to rewrite most of this area (linespecs). I mention this because on my archer-keiths-linespec-rewrite branch (which is CVS HEAD + my linespec rewrite patch), this appears to work: $ ./gdb -q gdb Reading symbols from /home/keiths/work/archer/linespec/linux/gdb/gdb...done. (top-gdb) b +0 Breakpoint 1 at 0x455153: file ../../archer/gdb/gdb.c, line 25. (top-gdb) r -nx -q Starting program: /home/keiths/work/archer/linespec/linux/gdb/gdb [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Breakpoint 1, main (argc=1, argv=0x7fffffffe0a8) at ../../archer/gdb/gdb.c:29 29 memset (&args, 0, sizeof args); Compare to CVS HEAD: $ ./gdb -nx -q gdb Reading symbols from /home/keiths/sources/gdb/git/virgin/linux/gdb/gdb...done. (top-gdb) b +0 Breakpoint 1 at 0x487343: file ../../gdb/gdb/gdb.c, line 20. (top-gdb) r -nx -q Starting program: /home/keiths/sources/gdb/git/virgin/linux/gdb/gdb -nx -q Error in re-setting breakpoint 1: No line 0 in file "../../gdb/gdb/gdb.c". [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". So when my patch is approved (might take many days yet), this should be working again. I'm afraid that doesn't help you much now, though... Keith