public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug cli/15642] Crash using 'rbreak'
Date: Tue, 18 Jun 2013 14:00:00 -0000	[thread overview]
Message-ID: <bug-15642-4717-A5mikBGDdc@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15642-4717@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=15642

Tom Tromey <tromey at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |WAITING
                 CC|                            |tromey at redhat dot com

--- Comment #1 from Tom Tromey <tromey at redhat dot com> ---
I think this is a bug in your host OS's C library; or at least in
"jimregexp.c", whatever that is.

According to POSIX, it is ok to pass NULL as this argument for regexec
as long as REG_NOSUB was used when initializing the regex_t.  And, I
think this is properly done.  See symtab.c:search_symbols.

However, something else odd is going on here.  I think the libiberty
regex.c should always be used.  I wonder why that isn't happening for
you.  You can look at the libiberty directory in the build tree to try
to find out.

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


  parent reply	other threads:[~2013-06-18 14:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-18  8:56 [Bug cli/15642] New: " vgiraud at neotion dot com
2013-06-18 10:19 ` [Bug cli/15642] " vgiraud at neotion dot com
2013-06-18 14:00 ` tromey at redhat dot com [this message]
2022-12-05  2:57 ` tromey at sourceware dot org

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-15642-4717-A5mikBGDdc@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).