public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "harry at harrydole dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/16439] rbreak . gives "unmatched quote" on Firefox
Date: Thu, 24 Jul 2014 20:35:00 -0000	[thread overview]
Message-ID: <bug-16439-4717-it9N99sBEh@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16439-4717@http.sourceware.org/bugzilla/>

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

harry at harrydole dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |harry at harrydole dot com

--- Comment #1 from harry at harrydole dot com ---
Perhaps this is a simpler "hello, world" example showing that "info function
<<.*string" works, but "rb <<.*string" returns the dreaded unmatched quote".

sh> cat hello.cpp
#include <iostream>

int main()
{
        std::cout << "hello, world" << std::endl;
        return 0;
}
sh> g++ --version
g++ (GCC) 4.7.2
Copyright (C) 2012 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

sh> g++ -g hello.cpp
sh> gdb a.out
GNU gdb (GDB) 7.5
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /remote/icwb1/hdole/p4/fw/xmain/src/bool/a.out...done.
(gdb) b 5
Breakpoint 1 at 0x400870: file hello.cpp, line 5.
(gdb) r
Starting program: /remote/icwb1/hdole/p4/fw/xmain/src/bool/a.out
warning: no loadable sections found in added symbol-file system-supplied DSO at
0x2aaaaaac7000

Breakpoint 1, main () at hello.cpp:5
5               std::cout << "hello, world" << std::endl;
(gdb) info function <<.*string
All functions matching regular expression "<<.*string":

File
/remote/depotsrc/depotsrc/amd64-2.6/gcc-4.7.2/x86_64-redhat-linux/libstdc++-v3/include/bits/basic_string.h:
std::basic_ostream<char, std::char_traits<char> > &std::operator<< <char,
std::char_traits<char>, std::allocator<char> >(std::basic_ostream<char,
std::char_traits<char> >&, std::basic_string<char, std::char_traits<char>,
std::allocator<char> > const&);
std::basic_ostream<wchar_t, std::char_traits<wchar_t> > &std::operator<<
<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t>
>(std::basic_ostream<wchar_t, std::char_traits<wchar_t> >&,
std::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> >
const&);
(gdb) rb <<.*string
unmatched quote

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


  reply	other threads:[~2014-07-24 20:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-12 18:31 [Bug breakpoints/16439] New: " techmeology.co.uk at gmail dot com
2014-07-24 20:35 ` harry at harrydole dot com [this message]
2024-01-08 17:31 ` [Bug breakpoints/16439] " ssbssa 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-16439-4717-it9N99sBEh@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).