public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "ssbssa at sourceware dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/25116] rbreak regexp does not work as expected
Date: Sat, 30 Dec 2023 12:20:43 +0000	[thread overview]
Message-ID: <bug-25116-4717-rWiLbJu4H8@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25116-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=25116

Hannes Domani <ssbssa at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
   Last reconfirmed|                            |2023-12-30
                 CC|                            |ssbssa at sourceware dot org
             Status|UNCONFIRMED                 |NEW

--- Comment #1 from Hannes Domani <ssbssa at sourceware dot org> ---
Character classes don't work because once a colon is found in the expression,
it uses the part before the colon as a filename qualification:

rbreak file:regex

    If rbreak is called with a filename qualification, it limits the search for
functions matching the given regular expression to the specified file.

Currently an empty filename qualification matches no file, so I wonder if we
could change it so an empty filename qualification matches all files, then we
could do something like this instead:

(gdb) rbreak :myNameSpace[[:digit:]]

And everything after the first colon would be the regexp, still matching all
files.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

           reply	other threads:[~2023-12-30 12:20 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <bug-25116-4717@http.sourceware.org/bugzilla/>]

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=bug-25116-4717-rWiLbJu4H8@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).