Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: "gdb-patches@sourceware.org ml" <gdb-patches@sourceware.org>
Subject: Re: [RFA 0/9] Explicit locations v2 - Introduction
Date: Thu, 15 May 2014 18:09:00 -0000	[thread overview]
Message-ID: <537502D2.5050705@redhat.com> (raw)
In-Reply-To: <20140515175649.GD4016@adacore.com>

On 05/15/2014 10:56 AM, Joel Brobecker wrote:

> I did a quick testing session of those patches. First of all, it passes
> our internal testsuite on x86_64-linux :).

Great news, thank you!

> The only part that I found to be odd was that I tried to be a little
> more selective in which operator I wanted to break on, by specifying
> the line number:
>
>      (gdb) b -f ops."-" -l 15
>      Breakpoint 4 at 0x401da4: -f ops."-" -l 15. (2 locations)
>
> I still got 2 locations, one of them not being at line 15:
>
>      (gdb) info break
>      4       breakpoint [...] <MULTIPLE>
>      4.1                [...]   0x0000000000401da4 in ops."-" at ops.adb:15
>      4.2                [...]   0x0000000000401ff3 in ops."-" at ops.adb:109
>
> But maybe this part wasn't part of this patch's objectives yet...

Right. Linespecs don't support this yet, either. This patch was simply 
to be at parity with linespec. When linespecs gain the ability, explicit 
should, too.

Keith


  reply	other threads:[~2014-05-15 18:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-08 17:56 Keith Seitz
2014-05-15 17:56 ` Joel Brobecker
2014-05-15 18:09   ` Keith Seitz [this message]
2014-05-15 20:03     ` Joel Brobecker
2014-10-12 19:50 ` Doug Evans

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=537502D2.5050705@redhat.com \
    --to=keiths@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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