public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Keith Seitz <keiths@redhat.com>, archer@sourceware.org
Subject: Re: [Archer] Re: [Archer] Re: [Archer] Stop the Insanity! Linespec Rewrite
Date: Wed, 07 Mar 2012 15:39:00 -0000	[thread overview]
Message-ID: <20120307153909.GY2867@adacore.com> (raw)
In-Reply-To: <87fwdkqwut.fsf@fleche.redhat.com>

> Pedro pointed out that your original note actually said that you thought
> "TASK" was accepted by Keith's branch, not CVS HEAD.
> But, this isn't the case, the code uses strncmp.
> So, I think there is no change in behavior here and everything is ok.

Aha, indeed, it's not what I thought.  I think that the "TASK" keyword
and what is behind it appears to be ignored when the "*" syntax is
used. The following works as expected:

    (gdb) break *break_me'address task 2
    Breakpoint 2 at 0x403a52: file /[...]/task_switch.adb, line 55.
    (gdb) info break
    [...]
    2       breakpoint     keep y   0x0000000000403a52 in task_switch.break_me 
                                    at /[...]/task_switch.adb:55 task 2
                                                                 ^^^^^^

The following accepts the command:

    (gdb) break *break_me'address TASK 2
    Note: breakpoint 2 also set at pc 0x403a52.
    Breakpoint 3 at 0x403a52: file /[...]/task_switch.adb, line 55.

But inserts a breakpoint without the task constraint:

    (gdb) info break
    [...]
    3       breakpoint     keep y   0x0000000000403a52 in task_switch.break_me 
                                    at /[...]/task_switch.adb:55

It might be something to do with the Ada expression parser?

-- 
Joel

  reply	other threads:[~2012-03-07 15:39 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-02  1:14 Keith Seitz
2012-03-02 17:00 ` Tom Tromey
2012-03-02 22:41   ` Keith Seitz
2012-03-03  2:36     ` Tom Tromey
2012-03-02 19:07 ` [Archer] " Joel Brobecker
2012-03-02 22:49   ` Keith Seitz
2012-03-06 17:40     ` [Archer] " Joel Brobecker
2012-03-06 19:08       ` Keith Seitz
2012-03-06 19:36         ` Keith Seitz
2012-03-06 21:50           ` [Archer] " Joel Brobecker
2012-03-07  0:11             ` [Archer] " Joel Brobecker
2012-03-07  1:08               ` Keith Seitz
2012-03-07  1:26                 ` [Archer] " Joel Brobecker
2012-03-07 14:39                   ` Tom Tromey
2012-03-07 15:01                     ` Tom Tromey
2012-03-07 15:39                       ` Joel Brobecker [this message]
2012-03-07 16:06                         ` [Archer] " Tom Tromey
2012-03-07 21:19                           ` Joel Brobecker
2012-03-07 21:11                         ` [Archer] " Keith Seitz
2012-03-08  3:02                           ` Joel Brobecker

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=20120307153909.GY2867@adacore.com \
    --to=brobecker@adacore.com \
    --cc=archer@sourceware.org \
    --cc=keiths@redhat.com \
    --cc=tromey@redhat.com \
    /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).