From: Keith Seitz <keiths@redhat.com>
To: Martin <lazarus@mfriebe.de>
Cc: gdb@sourceware.org
Subject: Re: possible regression in gdb 7.4 with -break-insert +0
Date: Wed, 21 Mar 2012 15:41:00 -0000 [thread overview]
Message-ID: <4F69F69D.2080803@redhat.com> (raw)
In-Reply-To: <4F69ED5D.1000006@mfriebe.de>
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
next prev parent reply other threads:[~2012-03-21 15:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 15:02 Martin
2012-03-21 15:41 ` Keith Seitz [this message]
2012-03-21 15:44 ` Keith Seitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F69F69D.2080803@redhat.com \
--to=keiths@redhat.com \
--cc=gdb@sourceware.org \
--cc=lazarus@mfriebe.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).